From: Daniel Phillips <phillips@bonn-fries.net>
To: Chris Mason <mason@suse.com>, linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, torvalds@transmeta.com
Subject: Re: [RFC] using writepage to start io
Date: Wed, 1 Aug 2001 03:01:17 +0200 [thread overview]
Message-ID: <01080103011705.00303@starship> (raw)
In-Reply-To: <233400000.996606471@tiny>
In-Reply-To: <233400000.996606471@tiny>
Hi, Chris
On Tuesday 31 July 2001 21:07, Chris Mason wrote:
> I had to keep some of the flush_dirty_buffer calls as page_launder
> wasn't triggering enough i/o on its own. What I'd like to do now is
> experiment with changing bdflush to only write pages off the inactive
> dirty lists.
Will kupdate continue to enforce the "no dirty buffer older than
XX" guarantee?
--
Daniel
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Phillips <phillips@bonn-fries.net>
To: Chris Mason <mason@suse.com>, linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, torvalds@transmeta.com
Subject: Re: [RFC] using writepage to start io
Date: Wed, 1 Aug 2001 03:01:17 +0200 [thread overview]
Message-ID: <01080103011705.00303@starship> (raw)
In-Reply-To: <233400000.996606471@tiny>
Hi, Chris
On Tuesday 31 July 2001 21:07, Chris Mason wrote:
> I had to keep some of the flush_dirty_buffer calls as page_launder
> wasn't triggering enough i/o on its own. What I'd like to do now is
> experiment with changing bdflush to only write pages off the inactive
> dirty lists.
Will kupdate continue to enforce the "no dirty buffer older than
XX" guarantee?
--
Daniel
--
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:[~2001-08-01 0:56 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-28 16:01 [RFC] using writepage to start io Chris Mason
2001-07-28 16:18 ` Alexander Viro
2001-07-28 16:25 ` Chris Mason
2001-07-31 19:07 ` Chris Mason
2001-07-31 19:07 ` Chris Mason
2001-08-01 1:01 ` Daniel Phillips [this message]
2001-08-01 1:01 ` Daniel Phillips
2001-08-01 2:05 ` Chris Mason
2001-08-01 2:05 ` Chris Mason
2001-08-01 14:57 ` Daniel Phillips
2001-08-01 14:57 ` Daniel Phillips
-- strict thread matches above, loose matches on Subject: below --
2001-08-05 18:34 Chris Mason
2001-08-05 18:34 ` Chris Mason
2001-08-05 22:38 ` Daniel Phillips
2001-08-05 22:38 ` Daniel Phillips
2001-08-05 23:32 ` Chris Mason
2001-08-05 23:32 ` Chris Mason
2001-08-06 5:39 ` Daniel Phillips
2001-08-06 5:39 ` Daniel Phillips
2001-08-06 13:24 ` Chris Mason
2001-08-06 13:24 ` Chris Mason
2001-08-06 16:13 ` Daniel Phillips
2001-08-06 16:13 ` Daniel Phillips
2001-08-06 16:51 ` Chris Mason
2001-08-06 16:51 ` Chris Mason
2001-08-06 19:45 ` Daniel Phillips
2001-08-06 19:45 ` Daniel Phillips
2001-08-06 20:12 ` Chris Mason
2001-08-06 20:12 ` Chris Mason
2001-08-06 21:18 ` Daniel Phillips
2001-08-06 21:18 ` Daniel Phillips
2001-08-07 11:02 ` Stephen C. Tweedie
2001-08-07 11:02 ` Stephen C. Tweedie
2001-08-07 11:39 ` Ed Tomlinson
2001-08-07 11:39 ` Ed Tomlinson
2001-08-07 18:36 ` Daniel Phillips
2001-08-07 18:36 ` Daniel Phillips
2001-08-07 12:07 ` Anton Altaparmakov
2001-08-07 12:07 ` Anton Altaparmakov
2001-08-07 12:02 ` Anton Altaparmakov
2001-08-07 12:02 ` Anton Altaparmakov
2001-08-07 13:29 ` Daniel Phillips
2001-08-07 13:29 ` Daniel Phillips
2001-08-07 13:31 ` Alexander Viro
2001-08-07 13:31 ` Alexander Viro
2001-08-07 15:52 ` Daniel Phillips
2001-08-07 15:52 ` Daniel Phillips
2001-08-07 14:23 ` Stephen C. Tweedie
2001-08-07 14:23 ` Stephen C. Tweedie
2001-08-07 15:51 ` Daniel Phillips
2001-08-07 15:51 ` Daniel Phillips
2001-08-08 14:49 ` Stephen C. Tweedie
2001-08-08 14:49 ` Stephen C. Tweedie
2001-08-06 15:13 ` Eric W. Biederman
2001-08-06 15:13 ` Eric W. Biederman
2001-08-07 15:19 Chris Mason
2001-08-07 15:19 ` Chris Mason
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=01080103011705.00303@starship \
--to=phillips@bonn-fries.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mason@suse.com \
--cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.