public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Moyer Jeff Moyer <jmoyer@redhat.com>
Cc: Jens Axboe <jaxboe@fusionio.com>, 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 14:36:11 -0400	[thread overview]
Message-ID: <20120501183610.GD18239@redhat.com> (raw)
In-Reply-To: <x49wr4vlpn8.fsf@segfault.boston.devel.redhat.com>

On Tue, May 01, 2012 at 02:31:07PM -0400, Jeff Moyer wrote:

[..]
> > But as to actual users, I really don't know. I agree it's probably not
> > that widely used. If google still had that code search, we could get a
> > better idea :-)
> 
> I know of one project: the venerable dump/restore utility uses CLONE_IO.

I thought you wrote cooperating queue logic to fix dump as it was not
using CLONE_IO and IO from multiple threads was going in separate 
queues.

Thanks
Vivek

  reply	other threads:[~2012-05-01 18:36 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 [this message]
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
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=20120501183610.GD18239@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=davej@redhat.com \
    --cc=jaxboe@fusionio.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox