From: Mike Christie <michaelc@cs.wisc.edu>
To: dgilbert@interlog.com
Cc: SCSI development list <linux-scsi@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
James Bottomley <james.bottomley@hansenpartnership.com>
Subject: Re: [PATCH] block SG_IO: add SG_FLAG_Q_AT_HEAD flag
Date: Wed, 11 Jun 2014 16:33:21 -0500 [thread overview]
Message-ID: <5398CB21.3000409@cs.wisc.edu> (raw)
In-Reply-To: <5390786E.8050601@interlog.com>
On 06/05/2014 09:02 AM, Douglas Gilbert wrote:
> After the SG_IO ioctl was copied into the block layer and
> later into the bsg driver, subtle differences emerged.
>
> One difference is the way injected commands are queued through
> the block layer (i.e. this is not SCSI device queueing nor SATA
> NCQ). Summarizing:
> - SG_IO on block layer device: blk_exec*(at_head=false)
> - sg device SG_IO: at_head=true
> - bsg device SG_IO: at_head=true
>
> Some time ago Boaz Harrosh introduced a sg v4 flag called
> BSG_FLAG_Q_AT_TAIL to override the bsg driver default. A
> recent patch titled: "sg: add SG_FLAG_Q_AT_TAIL flag"
> allowed the sg driver default to be overridden. This patch
> allows a SG_IO ioctl sent to a block layer device to have
> its default overridden.
>
> ChangeLog:
> - introduce SG_FLAG_Q_AT_HEAD flag in sg.h to cause
> commands that are injected via a block layer
> device SG_IO ioctl to set at_head=true
> - make comments clearer about queueing in sg.h since the
> header is used both by the sg device and block layer
> device implementations of the SG_IO ioctl.
> - introduce BSG_FLAG_Q_AT_HEAD in bsg.h for compatibility
> (it does nothing) and update comments.
>
>
> Signed-off-by: Douglas Gilbert <dgilbert@interlog.com>
Looks ok to me.
Reviewed-by: Mike Christie <michaelc@cs.wisc.edu>
prev parent reply other threads:[~2014-06-11 21:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 14:02 [PATCH] block SG_IO: add SG_FLAG_Q_AT_HEAD flag Douglas Gilbert
2014-06-05 14:35 ` Christoph Hellwig
2014-06-11 21:33 ` Mike Christie [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=5398CB21.3000409@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=dgilbert@interlog.com \
--cc=hch@infradead.org \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.