This is the mail archive of the
mailing list for the glibc project.
Re: DLOPEN and Statically linked executable
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Steve Munroe <sjmunroe at us dot ibm dot com>
- Cc: Peter Zaitsev <peter at mysql dot com>, libc-alpha at sources dot redhat dot com
- Date: Thu, 20 Jun 2002 17:53:03 +0200
- Subject: Re: DLOPEN and Statically linked executable
- References: <OF8AC5B644.037E523E-ON86256BDE.00506DD2@rchland.ibm.com>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Thu, Jun 20, 2002 at 10:36:03AM -0500, Steve Munroe wrote:
> Peter Zaitsev wrote:
> > At MySQL we use patched version of GLIBC for MySQL binary
> > distribution and so have to compile it statically. This patched
> > version of GLIBC is must to handle high load, it uses smaller thread
> > stack size instead of default 2M and has different mutex handling,
> > so less context switches will happen in case of MySQL and will give
> > better performance.
> Have you considered linking shared and using LD_PRELOAD to override
> any functions that are you would normally get from libc.so?
I think it would be better to figure why they need glibc changes.
E.g. the 2M thread stack size argument is very weak, since glibc on
sane architectures supports whatever thread stack size mysql wants.