From: Rene Herman <rene.herman@gmail.com>
To: Mike Galbraith <efault@gmx.de>
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 10:28:34 +0200 [thread overview]
Message-ID: <46A9ACB2.9030302@gmail.com> (raw)
In-Reply-To: <1185522844.6295.64.camel@Homer.simpson.net>
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.
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.
Rene.
--
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 8:28 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 ` Rene Herman [this message]
2007-07-27 9:26 ` updatedb Mike Galbraith
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=46A9ACB2.9030302@gmail.com \
--to=rene.herman@gmail.com \
--cc=andika@gmail.com \
--cc=ck@vds.kolivas.org \
--cc=efault@gmx.de \
--cc=false.hopes@gmail.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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