From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22033 invoked by alias); 25 Mar 2010 14:33:58 -0000 Received: (qmail 20449 invoked by uid 48); 25 Mar 2010 14:33:26 -0000 Date: Thu, 25 Mar 2010 14:33:00 -0000 From: "fche at redhat dot com" To: glibc-bugs@sources.redhat.com Message-ID: <20100325143324.11431.fche@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug libc/11431] New: consider madvise for ld.so X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2010-03/txt/msg00062.txt.bz2 Over the years, there have been several suggestions that ld.so use madvise(...WILLNEED) after mmapping a DT_NEEDED shared library to encourage more aggressive prefetching, which has been measured to help with certain large libraries such as firefox's. suse carries a glibc patch for this, and other projects have hacks in them to approximate this policy. After a brief bugzilla/google search, I haven't heard any official disposition of this heuristic. If it is known to be a bad idea, perhaps we can record the reasons for that here. -- Summary: consider madvise for ld.so Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: fche at redhat dot com CC: glibc-bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=11431 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.