From: Mike Galbraith <efault@gmx.de>
To: Rene Herman <rene.herman@gmail.com>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
Andika Triwidada <andika@gmail.com>,
Robert Deaton <false.hopes@gmail.com>,
linux-kernel@vger.kernel.org, ck list <ck@vds.kolivas.org>,
linux-mm@kvack.org
Subject: Re: updatedb
Date: Fri, 27 Jul 2007 11:26:08 +0200 [thread overview]
Message-ID: <1185528368.7851.44.camel@Homer.simpson.net> (raw)
In-Reply-To: <46A9ACB2.9030302@gmail.com>
On Fri, 2007-07-27 at 10:28 +0200, Rene Herman wrote:
> On 07/27/2007 09:54 AM, Mike Galbraith wrote:
>
> > On Fri, 2007-07-27 at 08:00 +0200, Rene Herman wrote:
> >
> >> The remaining issue of updatedb unnecessarily blowing away VFS caches is
> >> being discussed (*) in a few thread-branches still running.
> >
> > If you solve that, the swap thing dies too, they're one and the same
> > problem.
>
> I still wonder what the "the swap thing" is though. People just kept saying
> that swap-prefetch helped which would seem to indicate their problem didnt
> have anything to do with updatedb.
I haven't rummaged around in the VM in quite a long while, so don't know
exactly where the balance lies any more, and have never looked at
swap-prefetch, but the mechanism of how swap-prefetch can help the
"morning after syndrome" seems simple enough:
Reclaim (swapout) a slew of application pages because there are
truckloads of utterly bored pages laying about when updatedb comes along
and introduces memory pressure in the middle of the night. Updatedb
finishes, freeing some ram (doesn't matter how much) swap-prefetch
detects idle CPU, and begins faulting swapped out pages back in. In the
process of doing so, memory pressure is generated, and now these freshly
accessed pages are a less lovely target than the now aging VFS caches
that updatedb bloated up, so they shrink back down enough that the
balance you had before updatedb ran is restored... with the notable
exception that cached data is now toast, so what you gained by faulting
god knows how frequently used pages back in isn't _necessarily_ going to
help you. Heck, it could even step on what was left of your cached
working set after updatedb finished.
> Also, I know shit about the VFS so this may well be not very educated but to
> me something like FADV_NOREUSE on a dirfd sounds like a much more promising
> approach than the convoluted userspace schemes being discussed, if only
> because it'll actually be implemented/used.
I like Andrew's mention of a future option... put that sucker and
everybody who looks like him in a resource limited container.
-Mike
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-07-27 9:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 15:30 howto get a patch merged (WAS: Re: -mm merge plans for 2.6.23) Kacper Wysocki
2007-07-25 16:01 ` Rene Herman
2007-07-25 17:15 ` Robert Deaton
2007-07-26 3:59 ` updatedb Rene Herman
2007-07-26 6:23 ` updatedb Andika Triwidada
2007-07-26 7:49 ` updatedb Rene Herman
2007-07-26 9:37 ` updatedb Andika Triwidada
2007-07-27 0:46 ` updatedb Jesper Juhl
2007-07-27 6:00 ` updatedb Rene Herman
2007-07-27 7:54 ` updatedb Mike Galbraith
2007-07-27 8:28 ` updatedb Rene Herman
2007-07-27 9:26 ` Mike Galbraith [this message]
2007-07-27 11:09 ` updatedb Rene Herman
2007-07-27 11:48 ` updatedb Mike Galbraith
2007-07-27 12:28 ` updatedb Rene Herman
2007-07-27 13:32 ` updatedb Tilman Schmidt
2007-07-26 6:39 ` updatedb Bongani Hlope
2007-07-26 6:56 ` updatedb Rene Herman
2007-07-26 7:08 ` updatedb Bongani Hlope
2007-07-26 8:01 ` updatedb Rene Herman
2007-07-26 21:25 ` updatedb Bongani Hlope
2007-07-26 9:58 ` updatedb Björn Steinbrink
2007-07-26 10:23 ` updatedb Björn Steinbrink
2007-07-26 11:00 ` updatedb Rene Herman
2007-07-26 13:54 ` Re: howto get a patch merged (WAS: Re: -mm merge plans for 2.6.23) Jos Poortvliet
2007-07-25 16:07 ` Ingo Molnar
2007-07-25 16:40 ` [ck] " Michael Chang
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=1185528368.7851.44.camel@Homer.simpson.net \
--to=efault@gmx.de \
--cc=andika@gmail.com \
--cc=ck@vds.kolivas.org \
--cc=false.hopes@gmail.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rene.herman@gmail.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