From: Jeff Moyer <jmoyer@redhat.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] blk-plug: don't flush nested plug lists
Date: Tue, 07 Apr 2015 10:47:40 -0400 [thread overview]
Message-ID: <x49384cro4z.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <CACVXFVMtHf_SPGpEonfwwDLECS-5OOoyCMZUnukM2aYArVyg=Q@mail.gmail.com> (Ming Lei's message of "Tue, 7 Apr 2015 17:19:35 +0800")
Ming Lei <tom.leiming@gmail.com> writes:
> Hi Jeff,
Hi, Ming. Thanks for reviewing!
>> Unpatched kernel:
>> Read B/W: 283,638 KB/s
>> Read Merges: 0
>>
>> Patched kernel:
>> Read B/W: 873,224 KB/s
>> Read Merges: 2,046K
>
> The data is amazing, but maybe better to provide some latency
> data.
Yes, good point. I'll include the full fio output in the next posting.
>> Much of the patch involves modifying call sites to blk_start_plug,
>> since its signature is changed. The meat of the patch is actually
>
> I am wondering if the type of blk_start_plug has to be changed
> since the active plug is always the top plug with your patch, and
> blk_finish_plug() can find the active plug from current->plug.
That is a much simpler idea, thank you. I think blk_finish_plug
shouldn't take the plug argument, though, since it won't actually use
it.
Cheers,
Jeff
next prev parent reply other threads:[~2015-04-07 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 19:14 [PATCH 1/2] [v2] blk-mq: fix plugging in blk_sq_make_request Jeff Moyer
2015-04-06 19:14 ` [PATCH 2/2] blk-plug: don't flush nested plug lists Jeff Moyer
2015-04-07 9:19 ` Ming Lei
2015-04-07 14:47 ` Jeff Moyer [this message]
2015-04-08 17:38 ` Jens Axboe
2015-04-07 16:09 ` Shaohua Li
2015-04-08 17:56 ` Jeff Moyer
2015-04-16 15:47 ` Jeff Moyer
[not found] ` <x49wq1nrcoe.fsf_-_@segfault.boston.devel.redhat.com>
[not found] ` <20150408230203.GG15810@dastard>
2015-04-09 0:54 ` [PATCH 2/2][v2] " Dave Chinner
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=x49384cro4z.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.leiming@gmail.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
all inboxes | Powered by JetHome®