public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jaxboe@fusionio.com>
To: Christoph Hellwig <hch@lst.de>
Cc: "vgoyal@redhat.com" <vgoyal@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: cgq vs bdi names, was "cfq-iosched: fix a kernel OOPs when usb key  is inserted"
Date: Mon, 20 Sep 2010 15:12:44 +0200	[thread overview]
Message-ID: <4C975DCC.9050902@fusionio.com> (raw)
In-Reply-To: <20100920130318.GA29565@lst.de>

On 2010-09-20 15:03, Christoph Hellwig wrote:
> Hi Vivek, hi Jens,
> 
> where was http://git.kernel.dk/?p=linux-2.6-block.git;a=commitdiff_plain;h=44c74d6292e97f8bd9adfa6b0df3cb4f3c42a6dc posted  on the mailinglist?
> 
> I can't find it in my lkml or fsdevel inboxes.  Either way I don't think
> just papering over the underlying issue like this is a good idea.  
> 
> The big issue is that cfq tries to scanf the textual representation of
> the dev_t from the request_queue by abusing the bdi.  But the reason why
> we don't have a dev_t in the request_queue is that it's still not
> unique.  If it was we could easily add a dev_t into the request_queue
> and be done with it.
> 
> So the fix is either to get rid of the last remaining users of shared
> request_queues (IIRC the various floppy drivers) and just add a dev_t
> in the request_queue for the bdi, tracing and cfq, or add a dev_t into
> the request_queue and add a flag for shared request queues that the
> floppy driver and whoever needs it set and let the bdi sysfs code, cfq
> and blocktrace ignore theis request_queue.  This will also allow to
> get rid of the crap about ignoring failures due to already register
> or prematurely unregistered bdis and actually add real error handling
> to that code.

I did this one 15 months ago (according to git), but I never got it
tested:

http://git.kernel.dk/?p=linux-2.6-block.git;a=commitdiff;h=7a0ebc7ea1db42a71841df6a15be9fd420fae980

IIRC, the mtd stuff also uses a shared queue. But I think that is it.
Would indeed be VERY nice to finally get rid of that crap, it has
technically been outlawed since 2.5.1.

-- 
Jens Axboe


  reply	other threads:[~2010-09-20 13:12 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 [this message]
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
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=4C975DCC.9050902@fusionio.com \
    --to=jaxboe@fusionio.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@redhat.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