From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/3] writeback: simplify the write back thread queue
Date: Mon, 21 Jun 2010 09:49:03 +0200 [thread overview]
Message-ID: <20100621074903.GA28042@lst.de> (raw)
In-Reply-To: <4C1F18F9.4070206@kernel.dk>
On Mon, Jun 21, 2010 at 09:47:05AM +0200, Jens Axboe wrote:
> I'm fine with this, we can always bring back support for > 1 writeback
> thread per bdi when the need arises.
Note that this patch should actually make an eventual implementation
of > 1 writeback thread simpler if we want to go there - removing the
item from the list early means there is no need to deal with any kind of
race avoidance.
next prev parent reply other threads:[~2010-06-21 7:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 21:07 [PATCH 1/3] writeback: simplify the write back thread queue Christoph Hellwig
2010-06-20 8:40 ` Artem Bityutskiy
2010-06-20 9:00 ` Christoph Hellwig
2010-06-21 7:47 ` Jens Axboe
2010-06-21 7:49 ` Christoph Hellwig [this message]
2010-06-21 7:56 ` Jens Axboe
2010-06-21 8:01 ` Jens Axboe
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=20100621074903.GA28042@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=linux-fsdevel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).