From: Andrew Morton <akpm@digeo.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: William Lee Irwin III <wli@holomorphy.com>,
sfkaplan@cs.amherst.edu, linux-mm@kvack.org
Subject: Re: [PATCH] modified segq for 2.5
Date: Mon, 09 Sep 2002 14:52:45 -0700 [thread overview]
Message-ID: <3D7D182D.3514E0AD@digeo.com> (raw)
In-Reply-To: <Pine.LNX.4.44L.0209091808160.1857-100000@imladris.surriel.com>
Rik van Riel wrote:
>
> On Mon, 9 Sep 2002, Andrew Morton wrote:
> > Rik van Riel wrote:
>
> > > Move them to the inactive list the moment we're done writing
> > > them, that is, the moment we move on to the next page. We
> >
> > The moment "who" has done writing them? Some writeout
> > comes in via shrink_foo() and a ton of writeout comes in
> > via balance_dirty_pages(), pdflush, etc.
>
> generic_file_write, once that function moves beyond the last
> byte of the page, onto the next page, we can be pretty sure
> it's done writing to this page
Oh. So why don't we just start those new pages out on the
inactive list?
I fear that this change will result in us encountering more dirty
pages on the inactive list. It could be that moving then onto the
inactive list when IO is started is a good compromise - that will
happen pretty darn quick if the system is under dirty pressure
anyway.
Do we remove the SetPageReferenced() in generic_file_write?
--
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/
next prev parent reply other threads:[~2002-09-09 21:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 14:24 Rik van Riel
2002-09-09 9:38 ` Andrew Morton
2002-09-09 11:40 ` Ed Tomlinson
2002-09-09 17:10 ` William Lee Irwin III
2002-09-09 18:58 ` Andrew Morton
2002-09-09 13:10 ` Rik van Riel
2002-09-09 19:03 ` Andrew Morton
2002-09-09 19:25 ` Rik van Riel
2002-09-09 19:55 ` Andrew Morton
2002-09-09 20:03 ` Rik van Riel
2002-09-09 20:51 ` Andrew Morton
2002-09-09 20:57 ` Andrew Morton
2002-09-09 21:09 ` Rik van Riel
2002-09-09 21:52 ` Andrew Morton [this message]
2002-09-09 22:41 ` Rik van Riel
2002-09-10 0:17 ` Daniel Phillips
2002-09-09 22:49 ` William Lee Irwin III
2002-09-09 22:54 ` Rik van Riel
2002-09-09 23:32 ` William Lee Irwin III
2002-09-09 23:53 ` Rik van Riel
2002-09-09 22:46 ` Daniel Phillips
2002-09-09 22:58 ` Andrew Morton
2002-09-09 23:40 ` William Lee Irwin III
2002-09-10 0:02 ` Andrew Morton
2002-09-10 0:21 ` William Lee Irwin III
2002-09-10 1:13 ` Andrew Morton
2002-09-10 1:50 ` Daniel Phillips
2002-09-10 2:02 ` Rik van Riel
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=3D7D182D.3514E0AD@digeo.com \
--to=akpm@digeo.com \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=sfkaplan@cs.amherst.edu \
--cc=wli@holomorphy.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