From: Jens Axboe <jaxboe@fusionio.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Tejun Heo <tj@kernel.org>, Dave Jones <davej@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sasha Levin <levinsasha928@gmail.com>
Subject: Re: [PATCH v3.4-rc5] block: iocontext->nr_tasks should be initialized to one
Date: Tue, 1 May 2012 21:03:45 +0200 [thread overview]
Message-ID: <4FA03391.9010308@fusionio.com> (raw)
In-Reply-To: <x49obq7lorr.fsf@segfault.boston.devel.redhat.com>
On 2012-05-01 20:50, Jeff Moyer wrote:
> Jens Axboe <jaxboe@fusionio.com> writes:
>
>> On 2012-05-01 20:31, Jeff Moyer wrote:
>>> Jens Axboe <jaxboe@fusionio.com> writes:
>>> I know of one project: the venerable dump/restore utility uses CLONE_IO.
>>
>> Thanks Jeff, now I remember the specifics of what we tested. IIRC, we
>> also did numbers back then comparing the coop merging vs specifically
>> using CLONE_IO.
>
> Maybe? I picked through some old emails but couldn't find that exact
> comparison. It would have been a smart thing to do, though!
It might have been in a bugzilla thing, unfortunately. But yes, it'd be
the smart thing to do, hence I was pretty sure that you did it!
--
Jens Axboe
next prev parent reply other threads:[~2012-05-01 19:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 12:05 WARNING: at include/linux/iocontext.h:140 copy_io+0xb9/0x130() Sasha Levin
2012-05-01 16:17 ` [PATCH v3.4-rc5] block: iocontext->nr_tasks should be initialized to one Tejun Heo
2012-05-01 18:02 ` Jens Axboe
2012-05-01 18:09 ` Tejun Heo
2012-05-01 18:18 ` Jens Axboe
2012-05-01 18:31 ` Jeff Moyer
2012-05-01 18:36 ` Vivek Goyal
2012-05-01 18:48 ` Jeff Moyer
2012-05-01 18:59 ` Vivek Goyal
2012-05-01 19:04 ` Jeff Moyer
2012-05-01 19:08 ` Vivek Goyal
2012-05-01 18:37 ` Jens Axboe
2012-05-01 18:50 ` Jeff Moyer
2012-05-01 19:03 ` Jens Axboe [this message]
2012-05-01 18:04 ` Jens Axboe
2012-05-01 18:06 ` Tejun Heo
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=4FA03391.9010308@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=davej@redhat.com \
--cc=jmoyer@redhat.com \
--cc=levinsasha928@gmail.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 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.