[Mesa-dev] [PATCH] src: replace RTLD_NOW with RTLD_LAZY

Enrico Weigelt, metux IT consult enrico.weigelt at gr13.net
Sat Aug 6 08:28:42 UTC 2016


On 06.08.2016 04:05, ⚛ wrote:

> Question 2: Exists there a reason for _not_ linking radeonsi_dri.so,
> swrastg_dri.so, etc, directly to Mesa's libGL.so? The Gallium
> *_dri.so libraries are the same inode on the filesystem.

Sure about that ?

nekrad at orion:~/MESA/lib/dri$ ls -lai
total 508348
6750710 drwxrwxr-x 2 nekrad nekrad     4096 Aug  3 03:50 .
6750702 drwxrwxr-x 4 nekrad nekrad     4096 Aug  3 03:50 ..
6714176 -rwxr-xr-x 5 nekrad nekrad 51025670 Aug  3 03:50 i915_dri.so
6714176 -rwxr-xr-x 5 nekrad nekrad 51025670 Aug  3 03:50 i965_dri.so
6714275 -rwxr-xr-x 5 nekrad nekrad 53071749 Aug  3 03:50 kms_swrast_dri.so
6714176 -rwxr-xr-x 5 nekrad nekrad 51025670 Aug  3 03:50
nouveau_vieux_dri.so
6714176 -rwxr-xr-x 5 nekrad nekrad 51025670 Aug  3 03:50 r200_dri.so
6714275 -rwxr-xr-x 5 nekrad nekrad 53071749 Aug  3 03:50 r300_dri.so
6714275 -rwxr-xr-x 5 nekrad nekrad 53071749 Aug  3 03:50 r600_dri.so
6714176 -rwxr-xr-x 5 nekrad nekrad 51025670 Aug  3 03:50 radeon_dri.so
6714275 -rwxr-xr-x 5 nekrad nekrad 53071749 Aug  3 03:50 swrast_dri.so
6714275 -rwxr-xr-x 5 nekrad nekrad 53071749 Aug  3 03:50 vmwgfx_dri.so

I see only some of them are the same.
By the way: why not using symlinks here ?

(hardlinks can easily break up ...)

> Question 3: Isn't the current status quo (i.e: not linking
> radeonsi_dri.so directly to libGL.so) also a micro-optimization that
> can hide certain bugs?

Just curious: how much space would it add if drivers were linked
into libGL.so ? (IOW: how much redundancy is there between the
individual *_dri.so's ?)

--mtx



More information about the mesa-dev mailing list