public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Taras Glek <tglek@mozilla.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Downsides to madvise/fadvise(willneed) for application startup
Date: Tue, 06 Apr 2010 15:09:21 -0700	[thread overview]
Message-ID: <4BBBB111.7080804@mozilla.com> (raw)
In-Reply-To: <adaljd1790c.fsf@roland-alpha.cisco.com>

On 04/05/2010 04:52 PM, Roland Dreier wrote:
> Almost certainly teaching my grandmother to suck eggs, but are you aware
> of the work Michael Meeks has done on improving openoffice.org startup time?
>    
Yes. There were some stones left unturned in the cold startup area. 
Turns out that every single large application suffers from low io 
throughput likely due to lack of cooperation between the dynamic linker 
and the kernel.
There is a glibc bug filed on that.

http://sourceware.org/bugzilla/show_bug.cgi?id=11431

Unfortunately, few userspace people seem to know exactly how madvise() 
hints behave, so I was hoping someone on LKML would clue me in.

Taras

  reply	other threads:[~2010-04-06 22:09 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-05 22:43 Downsides to madvise/fadvise(willneed) for application startup Taras Glek
2010-04-05 23:17 ` Dave Chinner
2010-04-05 23:52 ` Roland Dreier
2010-04-06 22:09   ` Taras Glek [this message]
2010-04-06  9:51 ` Johannes Weiner
2010-04-06 21:57   ` Taras Glek
2010-04-06 22:26     ` Johannes Weiner
2010-04-06 22:39       ` Taras Glek
2010-04-07  2:24   ` Wu Fengguang
2010-04-07  2:54     ` Taras Glek
2010-04-07  4:06       ` Minchan Kim
2010-04-07  7:14         ` Wu Fengguang
2010-04-07  7:33           ` Minchan Kim
2010-04-07  7:47             ` Wu Fengguang
2010-04-07  8:06               ` Minchan Kim
2010-04-07  8:13                 ` Wu Fengguang
2010-04-07  7:38       ` Wu Fengguang
2010-04-08 17:44         ` Taras Glek
2010-04-12  2:27           ` Wu Fengguang
2010-04-12  3:25             ` Minchan Kim
2010-04-12  4:58               ` Wu Fengguang
2010-04-12  4:43             ` drepper
2010-04-12  4:46               ` Taras Glek
2010-04-12  4:50               ` Wu Fengguang
2010-04-12  8:50 ` Andi Kleen
2010-04-15 22:53 ` Andrew Morton
2010-04-15 23:21   ` Zan Lynx
2010-04-15 20:42     ` Andrew Morton
2010-04-16 11:41     ` Andi Kleen
2010-04-16 12:23       ` Theodore Tso
2010-04-16 12:23       ` Theodore Tso
2010-04-16  0:41   ` Taras Glek
2010-04-15 22:21     ` Andrew Morton
2010-04-16  2:37       ` Taras Glek
2010-04-16 11:40   ` Andi Kleen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BBBB111.7080804@mozilla.com \
    --to=tglek@mozilla.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdreier@cisco.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox