From: Douglas Gilbert <dgilbert@interlog.com>
To: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>
Cc: linux-block@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] bsg: deprecate BIDI support in bsg
Date: Thu, 20 Dec 2018 13:19:40 -0500 [thread overview]
Message-ID: <43c65430-2dbe-9063-3dd4-4941751c323e@interlog.com> (raw)
In-Reply-To: <b9d89b97-9f9d-b586-ff89-61bafaecd5cc@kernel.dk>
On 2018-12-20 12:09 p.m., Jens Axboe wrote:
> On 12/20/18 12:12 AM, Christoph Hellwig wrote:
>> On Wed, Dec 19, 2018 at 04:23:14PM -0700, Jens Axboe wrote:
>>> On 12/19/18 7:39 AM, Christoph Hellwig wrote:
>>>> Besides the OSD command set that never got traction, the only SCSI
>>>> command using bidirectional buffers is XDWRITEREAD in the 10 and 32
>>>> byte variants, which is extremely esoteric. It probably doesn't make
>>>> sense to keep the support code around just for that, so start
>>>> deprecating the support.
>>>
>>> Acked-by: Jens Axboe <axboe@kernel.dk>
>>
>> You are the bsg maintainer, so I expected you to pick it up :)
>
> OK - did you to amend the commit message to reflect the death of
> XDWRITEREAD as well?
>
It was made obsolete in _draft_ sbc4r15.pdf according to my notes.
It is not "dead", not until SBC-4 is ratified. Until then, SBC-3 is the
current SCSI "block" device standard and it is there as a non-mandatory
command.
Doug Gilbert
prev parent reply other threads:[~2018-12-20 18:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 14:39 [PATCH] bsg: deprecate BIDI support in bsg Christoph Hellwig
2018-12-19 23:07 ` Bart Van Assche
2018-12-20 7:12 ` Christoph Hellwig
2018-12-19 23:23 ` Jens Axboe
2018-12-20 7:12 ` Christoph Hellwig
2018-12-20 17:09 ` Jens Axboe
2018-12-20 18:19 ` Douglas Gilbert [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=43c65430-2dbe-9063-3dd4-4941751c323e@interlog.com \
--to=dgilbert@interlog.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox