This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: [PATCH] Use madvise in glibc
- From: Ulrich Drepper <drepper at redhat dot com>
- To: Thorsten Kukuk <kukuk at suse dot de>
- Cc: libc-alpha at sources dot redhat dot com
- Date: Fri, 23 Jul 2004 12:13:37 -0700
- Subject: Re: [PATCH] Use madvise in glibc
- Organization: Red Hat, Inc.
- References: <20040723134611.GA22391@suse.de>
You need data which shows that this is actually buying anything. I have
experimented with this some time back and nothing really made a
difference. Maybe it made things even worse. Consider unstripped DSOs
of which only a fraction is actually mapped into memory. And large DSOs
where only little pieces of code and data are used.
madvise etc would make sense if we could determine the frequently used
parts of DSOs and get those functions/data close together in the DSO.
Then these regions could be prefaulted or madvise can be used. But a
general madvise is probably not buying anything. Well, prove me wrong.
--
â Ulrich Drepper â Red Hat, Inc. â 444 Castro St â Mountain View, CA â