From: James Bottomley <James.Bottomley@SteelEye.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
linux-ide@vger.kernel.org, Jens Axboe <Jens.Axboe@oracle.com>
Subject: Re: [PATCH] block: add protocol discriminators to requests and queues
Date: Thu, 02 Aug 2007 13:59:40 -0500 [thread overview]
Message-ID: <1186081180.3449.24.camel@localhost.localdomain> (raw)
In-Reply-To: <20070802185128.GL21219@parisc-linux.org>
On Thu, 2007-08-02 at 12:51 -0600, Matthew Wilcox wrote:
> On Thu, Aug 02, 2007 at 12:47:25PM -0500, James Bottomley wrote:
> > This looks small and innocuous, but it's actually the beginning of
> > moving the upper layer drivers into block and adding a filtering layer.
> > The idea is that the queue contains a queue_protocol parameter which
> > details what the device actually speaks. The requests are likewise
> > filled in with a cmd_protocol parameter by the ULDs (or bsg if it's a
> > user initiated command, using the existing sgv4 protocol fields).
> >
> > Now we have the capability of adding say native ATA pass through to BSG,
> > but also we can add things like an ATAPI filter: sr creates SCSI
> > requests, but these could be sent through a PACKET_COMMAND wrapper and
> > emerge as BLK_PROTOCOL_ATAPI before being sent to the device. Likewise,
> > sd requests going to BLK_PROTOCOL_ATA devices would have to go through
> > SATL filters.
>
> Will it also add the ability to add device-specific filters? For
> example, the CD burners that have manufacturer specific opcodes to turn
> on various features that are safe for users to use ... but have to be
> limited to root-only currently as we can't know what kind of device the
> command is going to.
I wasn't planning on doing this ... the idea is basically a protocol
conversion filter. Device quirks don't quite fit into this model.
James
prev parent reply other threads:[~2007-08-02 18:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 17:47 [PATCH] block: add protocol discriminators to requests and queues James Bottomley
2007-08-02 18:51 ` Matthew Wilcox
2007-08-02 18:59 ` James Bottomley [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=1186081180.3449.24.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=Jens.Axboe@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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