linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Robert Deaton" <false.hopes@gmail.com>
To: Rene Herman <rene.herman@gmail.com>
Cc: linux-kernel@vger.kernel.org, ck list <ck@vds.kolivas.org>,
	linux-mm@kvack.org
Subject: Re: howto get a patch merged (WAS: Re: -mm merge plans for 2.6.23)
Date: Wed, 25 Jul 2007 13:15:49 -0400	[thread overview]
Message-ID: <a491f91d0707251015x75404d9fld7b3382f69112028@mail.gmail.com> (raw)
In-Reply-To: <46A773EA.5030103@gmail.com>

On 7/25/07, Rene Herman <rene.herman@gmail.com> wrote:
> And there we go again -- off into blabber-land. Why does swap-prefetch help
> updatedb? Or doesn't it? And if it doesn't, why should anyone trust anything
> else someone who said it does says?

I don't think anyone has ever argued that swap-prefetch directly helps
the performance of updatedb in any way, however, I do recall people
mentioning that updatedb, being a ram intensive task, will often cause
things to be swapped out while it runs on say a nightly cronjob. If a
person is not at their computer, updatedb will run, cause all their
applications to be swapped out, finish its work, and exit, leaving all
the other applications that would have otherwise been left in RAM for
when the user returns to his/her computer in swap. Thus, when someone
returns, you have to wait for all your applications to be swapped back
in.

Swap prefetch, on the other hand, would have kicked in shortly after
updatedb finished, leaving the applications in swap for a speedy
recovery when the person comes back to their computer.

-- 
--Robert Deaton

--
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>

  reply	other threads:[~2007-07-25 17:15 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25 15:30 Kacper Wysocki
2007-07-25 16:01 ` Rene Herman
2007-07-25 17:15   ` Robert Deaton [this message]
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                 ` 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=a491f91d0707251015x75404d9fld7b3382f69112028@mail.gmail.com \
    --to=false.hopes@gmail.com \
    --cc=ck@vds.kolivas.org \
    --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