From: Jens Axboe <axboe@kernel.dk>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org, Jan Kara <jack@suse.cz>,
Fengguang Wu <fengguang.wu@intel.com>,
Jeff Moyer <jmoyer@redhat.com>
Subject: Re: [GIT PULL] writeback: convert writeback to unbound workqueue
Date: Tue, 2 Apr 2013 11:53:53 +0200 [thread overview]
Message-ID: <20130402095353.GB4667@kernel.dk> (raw)
In-Reply-To: <20130402030933.GB6255@htj.dyndns.org>
On Mon, Apr 01 2013, Tejun Heo wrote:
> Hello, Jens.
>
> This is the pull request for the earlier patchset[1] with the same
> name. It's only three patches (the first one was committed to
> workqueue tree) but the merge strategy is a bit involved due to the
> dependencies.
>
> * Because the conversion needs features from wq/for-3.10,
> block/for-3.10/core is based on rc3, and wq/for-3.10 has conflicts
> with rc3, I pulled mainline (rc5) into wq/for-3.10 to prevent those
> workqueue conflicts from flaring up in block tree.
>
> * Resolving the issue that Jan and Dave raised about debugging
> requires arch-wide changes. The patchset is being worked on[2] but
> it'll have to go through -mm after these changes show up in -next,
> and not included in this pull request.
>
> The three commits are located in the following git branch.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git writeback-workqueue
>
> Pulling it into block/for-3.10/core produces a conflict in
> drivers/md/raid5.c between the following two commits.
>
> e3620a3ad5 ("MD RAID5: Avoid accessing gendisk or queue structs when not available")
> 2f6db2a707 ("raid5: use bio_reset()")
>
> The conflict is trivial - one removes an "if ()" conditional while the
> other removes "rbi->bi_next = NULL" right above it. We just need to
> remove both. The merged branch is available at
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git block-test-merge
>
> so that you can use it for verification. The test merge commit has
> proper merge description.
>
> While these changes are a bit of pain to route, they make code simpler
> and even have, while minute, measureable performance gain[3] even on a
> workload which isn't particularly favorable to showing the benefits of
> this conversion.
Thanks, pulled in for testing. We'll need the debug change in before
sending this upstream, though. I agree with Jan/Dave that this is
required functionality, for debugging purposes.
--
Jens Axboe
next prev parent reply other threads:[~2013-04-02 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 3:09 [GIT PULL] writeback: convert writeback to unbound workqueue Tejun Heo
2013-04-02 9:53 ` Jens Axboe [this message]
2013-04-02 16:20 ` Tejun Heo
2013-04-03 11:47 ` 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=20130402095353.GB4667@kernel.dk \
--to=axboe@kernel.dk \
--cc=fengguang.wu@intel.com \
--cc=jack@suse.cz \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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