From: Jens Axboe <axboe@suse.de>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Rik van Riel <riel@conectiva.com.br>,
Linus Torvalds <torvalds@transmeta.com>,
Chris Mason <mason@suse.com>,
linux-mm@kvack.org
Subject: Re: [PATCH] kill flush_dirty_buffers
Date: Tue, 7 Aug 2001 23:19:41 +0200 [thread overview]
Message-ID: <20010807231941.A4587@suse.de> (raw)
In-Reply-To: <0108062153340J.00294@starship>
On Mon, Aug 06 2001, Daniel Phillips wrote:
> This suggests that buffer flushing needs to be per-device.
Yep, and either stopped as soon as the queue free lists are empty or
done independently per queue. One thought I had was to actually move the
dirty list to the queues (or at least separated) and have the plugs
_pull_ the buffers out instead of the other way around.
--
Jens Axboe
--
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-07 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-06 17:09 Chris Mason
2001-08-06 18:00 ` Linus Torvalds
2001-08-06 18:39 ` Rik van Riel
2001-08-06 19:53 ` Daniel Phillips
2001-08-07 21:19 ` Jens Axboe [this message]
2001-08-06 21:14 ` 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=20010807231941.A4587@suse.de \
--to=axboe@suse.de \
--cc=linux-mm@kvack.org \
--cc=mason@suse.com \
--cc=phillips@bonn-fries.net \
--cc=riel@conectiva.com.br \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox