From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/3] writeback: simplify the write back thread queue
Date: Mon, 21 Jun 2010 09:47:05 +0200 [thread overview]
Message-ID: <4C1F18F9.4070206@kernel.dk> (raw)
In-Reply-To: <20100619210756.GA29875@lst.de>
On 2010-06-19 23:07, Christoph Hellwig wrote:
> First remove items from work_list as soon as we start working on them. This
> means we don't have to track any pending or visited state and can get
> rid of all the RCU magic freeing the work items - we can simply free
> them once the operation has finished. Second use a real completion for
> tracking synchronous requests - if the caller sets the completion pointer
> we complete it, otherwise use it as a boolean indicator that we can free
> the work item directly. Third unify struct wb_writeback_args and struct
> bdi_work into a single data structure, wb_writeback_work. Previous we
> set all parameters into a struct wb_writeback_args, copied it into
> struct bdi_work, copied it again on the stack to use it there. Instead
> of just allocate one structure dynamically or on the stack and use it
> all the way through the stack.
I'm fine with this, we can always bring back support for > 1 writeback
thread per bdi when the need arises.
--
Jens Axboe
next prev parent reply other threads:[~2010-06-21 7:47 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 [this message]
2010-06-21 7:49 ` Christoph Hellwig
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=4C1F18F9.4070206@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--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 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.