From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Shaohua Li <shaohua.li@intel.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch 2/2]block: recursive merge requests
Date: Fri, 16 Dec 2011 21:16:05 +0100 [thread overview]
Message-ID: <4EEBA705.7060900@kernel.dk> (raw)
In-Reply-To: <20111216193414.GA30654@infradead.org>
On 2011-12-16 20:34, Christoph Hellwig wrote:
> On Fri, Dec 16, 2011 at 09:52:43AM +0800, Shaohua Li wrote:
>> With recursive merge below, the workload throughput gets improved 20%
>> and context switch drops 60%.
>
> What workload and what filesystem?
It shouldn't really matter for the quoted case, where you have 2
processes issuing interleaved reads.
--
Jens Axboe
prev parent reply other threads:[~2011-12-16 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 1:52 Shaohua Li
2011-12-16 12:59 ` Jens Axboe
2011-12-16 19:34 ` Christoph Hellwig
2011-12-16 20:16 ` Jens Axboe [this message]
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=4EEBA705.7060900@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.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
Powered by JetHome