From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Christoph Hellwig <hch@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@osdl.org>,
ppc64-dev <linuxppc64-dev@ozlabs.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PPC64 iSeries: don't share request queues in viocd
Date: Mon, 15 Nov 2004 22:44:33 +1100 [thread overview]
Message-ID: <419896A1.50605@yahoo.com.au> (raw)
In-Reply-To: <20041115113410.GA14471@infradead.org>
Christoph Hellwig wrote:
> On Mon, Nov 15, 2004 at 04:53:57PM +1100, Stephen Rothwell wrote:
>
>>Hi Andrew,
>>
>>This patch fixes the virtual cdrom driver to not share a single request
>>queue. Sharing the queue causes an oops if you remove the module and more
>>than one cdrom exists.
>
>
> Maybe you should fix that underlying bug? Queues are supposed to be
> shareable.
>
I think shared queues are actually quite fundamentally broken at the
moment (as pointed out to me by Al). It stems from the refcounting /
conceptual relationship between a gendisk and a queue (I think - been
a while since I looked at the code).
I had something which just about fixed it up except that I couldn't
work out an appropriate place and name for the "queue" in the sysfs
hierarcy (IIRC I just had it as a sequentially increasing number, in
/sys/block/).
It is a relationship that I don't think sysfs can capture very well:
queues are shared between multiple other objects, but they have no
meaning outside the context of one of these objects.
prev parent reply other threads:[~2004-11-15 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 5:53 [PATCH] PPC64 iSeries: don't share request queues in viocd Stephen Rothwell
2004-11-15 11:34 ` Christoph Hellwig
2004-11-15 11:44 ` Nick Piggin [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=419896A1.50605@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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