mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Mielke <mark@mark.mielke.cc>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Robert Love <rml@tech9.net>,
	Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: More on O_STREAMING (goodby read pauses)
Date: Thu, 10 Oct 2002 14:01:08 -0400	[thread overview]
Message-ID: <20021010180108.GB16962@mark.mielke.cc> (raw)
In-Reply-To: <20021010143927.GA2193@werewolf.able.es>

On Thu, Oct 10, 2002 at 04:39:27PM +0200, J.A. Magallon wrote:
> On 2002.10.10 Mark Mielke wrote:
> >I assume the stall is not 'while pages are sent to disk', but rather
> >until kswapd gets around to freeing enough pages to allow memory to
> >fill again. The stall is due to the pages being fully analyzed to
> >determine which ones should go, and which ones shouldn't. O_STREAMING
> >removes the pages ahead of time, so no analysis is ever required.
> I can _hear_ the disk activity when the stall happens, so selecting what
> to drop is fast, but then you have to write it...

I don't think this is right. Prove me wrong by explaining how kswapd works,
but if a page isn't dirty, there is no need to write it out to disk.

My (perhaps incorrect) assumption is that kswapd prefers to swap on clean
pages over dirty pages. If your pages are mostly clean, there is nothing
to write to disk the clear majority of the time.

Clean read-only pages should *never* be written to swap. They can be re-read
from their source.

I _think_ what you are seeing is that kswapd is not cleaning pages out
fast enough, which means that *other* tasks executing need to have their
*swapped out* pages *read* from disk. I.e. the churning you hear is probably
mostly reads - not writes.

mark

-- 
mark@mielke.cc/markm@ncf.ca/markm@nortelnetworks.com __________________________
.  .  _  ._  . .   .__    .  . ._. .__ .   . . .__  | Neighbourhood Coder
|\/| |_| |_| |/    |_     |\/|  |  |_  |   |/  |_   | 
|  | | | | \ | \   |__ .  |  | .|. |__ |__ | \ |__  | Ottawa, Ontario, Canada

  One ring to rule them all, one ring to find them, one ring to bring them all
                       and in the darkness bind them...

                           http://mark.mielke.cc/


  reply	other threads:[~2002-10-10 17:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-09 22:23 J.A. Magallon
2002-10-09 22:43 ` Robert Love
2002-10-10  3:40   ` Mark Mielke
2002-10-10 14:39     ` J.A. Magallon
2002-10-10 18:01       ` Mark Mielke [this message]
2002-10-10 22:50         ` J.A. Magallon
2002-10-10 23:06           ` Andrew Morton
2002-10-11  2:04           ` Mark Mielke
2002-10-11  8:13 Samium Gromoff

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=20021010180108.GB16962@mark.mielke.cc \
    --to=mark@mark.mielke.cc \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    /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

all inboxes | Powered by JetHome®