On Thu, 6 Oct 2011 13:24:20 +0200 (CEST), Fabio <fabio....@libero.it> wrote: > >Da: kei...@vmware.com > >Data: 05/10/2011 11.39 > >A: "Christopher James Halse Rogers"<christopher.halse.rog...@canonical.com> > >Cc: "Joakim Sindholt"<opensou...@zhasha.com>, <mesa-dev@lists.freedesktop. > org>, "Fabio"<fabio....@libero.it> > >Ogg: Re: [Mesa-dev] libgallium.so and miscelaneous buildsystem patches > > > >On Wed, 2011-10-05 at 20:14 +1100, Christopher James Halse Rogers wrote: > >> On Wed, 2011-10-05 at 09:24 +0200, Joakim Sindholt wrote: > >> > On Tue, 2011-10-04 at 17:58 +0200, Fabio wrote: > >> > > Can the patches at > >> > > http://lists.freedesktop.org/archives/mesa-dev/2011-August/011099.html > >> > > be considered for merging? > >> > > > >> > > Sharing libgallium should save some MB of installed space. > >> > > >> > And be an ABI nightmare for distributions > >> > >> No; it's a private library. Distributions will happily ship a > >> libgallium built from exactly the same source that the DRI drivers are > >> built from. Indeed, that's what currently happens for those > >> distributions with ship with --enable-shared-dricore, and what happens > >> in Ubuntu, where we've got this patch series applied in our never-ending > >> quest to cram a fully-featured linux system on a 700MB CD. > >> > >> Saving 20-odd megabytes is really useful there :) > > > >An alternative would be to build all the drivers into a single library > >for maximal sharing. > > A single library with all the drivers will however be bigger (compared to the > single driver + eventual shared libs) and it would use more memory.
It would be larger than any one of the drivers, but I don't see how it would be larger than the sum of the split drivers plus the shared code, which is what matters for disks. And, with paging, I don't see how it would use more memory at runtime.
pgpk6VwRfojkF.pgp
Description: PGP signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
