From: Vivek Goyal <vgoyal@redhat.com>
To: Jens Axboe <jaxboe@fusionio.com>
Cc: Christoph Hellwig <hch@lst.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Maxim Levitsky <maximlevitsky@gmail.com>
Subject: Re: [PATCH] floppy: switch to one queue per drive instead of sharing a queue (Was: Re: cgq vs bdi names, was "cfq-iosched: fix a kernel OOPs when usb key is inserted")
Date: Wed, 22 Sep 2010 16:42:16 -0400 [thread overview]
Message-ID: <20100922204216.GA7487@redhat.com> (raw)
In-Reply-To: <4C992F12.5090000@fusionio.com>
On Wed, Sep 22, 2010 at 12:17:54AM +0200, Jens Axboe wrote:
[..]
> Super, thanks a lot! I will queue this up. If you want to continue
> this (very noble) crusade, the next target is
> drivers/mtd/mtd_blkdevs.c. I never got that one started, but it was
> next on my list.
Hi Jens,
IIUC, for MTD this conversion is already done and we seem to be using separate
request queue for each gendisk instead of some disks sharing a single
request queue. I think by following is relevant commit. Maxim should be
able to confirm though.
-----------------------------------------------------------------------
commit a863862257b7dd08d855bafcb0aedd9ad848ed91
Author: Maxim Levitsky <maximlevitsky@gmail.com>
Date: Mon Feb 22 20:39:29 2010 +0200
mtd: blktrans: remove mtd_blkcore_priv, switch to per device queue and
threa
This is the biggest change. To make hotplug possible, and this layer
clean, the mtd_blktrans_dev now contains everything for a single mtd
block translation device. Also removed some very old leftovers.
Signed-off-by: Maxim Levitsky <maximlevitsky@gmail.com>
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
-----------------------------------------------------------------------
I did create two mtd devices (from block devices, block2mtd), then then
created two block devices on top of those mtd devices (using mtdblock)
and these two devices mtdblock0 and mtdblock1 seems to be using their
own separate request queues. (Change in ioscheduler on one does not change
it on other queue).
So to me it looks like MTD is all set, until and unless I am missing
something.
Vivek
next prev parent reply other threads:[~2010-09-22 20:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 13:03 cgq vs bdi names, was "cfq-iosched: fix a kernel OOPs when usb key is inserted" Christoph Hellwig
2010-09-20 13:12 ` Jens Axboe
2010-09-20 22:30 ` [PATCH] floppy: switch to one queue per drive instead of sharing a queue (Was: Re: cgq vs bdi names, was "cfq-iosched: fix a kernel OOPs when usb key is inserted") Vivek Goyal
2010-09-21 18:25 ` Vivek Goyal
2010-09-21 22:17 ` Jens Axboe
2010-09-22 20:42 ` Vivek Goyal [this message]
2010-09-23 7:59 ` Jens Axboe
2010-09-23 8:05 ` Christoph Hellwig
2010-09-23 21:40 ` Vivek Goyal
2010-09-20 13:32 ` cgq vs bdi names, was "cfq-iosched: fix a kernel OOPs when usb key is inserted" Vivek Goyal
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=20100922204216.GA7487@redhat.com \
--to=vgoyal@redhat.com \
--cc=hch@lst.de \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maximlevitsky@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