From: Jens Axboe <jens.axboe@oracle.com>
To: Douglas Gilbert <dougg@torque.net>
Cc: FUJITA Tomonori <tomof@acm.org>,
linux-scsi@vger.kernel.org, fujita.tomonori@lab.ntt.co.jp
Subject: Re: [PATCH] unexport sg v3 helper functions
Date: Tue, 24 Jul 2007 13:34:33 +0200 [thread overview]
Message-ID: <20070724113433.GR3287@kernel.dk> (raw)
In-Reply-To: <46A5E12E.2060804@torque.net>
On Tue, Jul 24 2007, Douglas Gilbert wrote:
> Jens Axboe wrote:
> > On Mon, Jul 23 2007, Douglas Gilbert wrote:
> >> Jens Axboe wrote:
> >>> On Sun, Jul 22 2007, FUJITA Tomonori wrote:
> >>>> blk_fill_sghdr_rq, blk_unmap_sghdr_rq, and blk_complete_sghdr_rq were
> >>>> exported for bsg, however bsg was changed to support only sg v4.
> >>>>
> >>>> Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> >>> Acked-by: Jens Axboe <jens.axboe@oracle.com>
> >> Why?
> >
> > The reasoning is right there, a few lines up - bsg doesn't support sg v3
> > commands.
>
> I can read.
Then write better questions "Why?" isn't very useful.
> Why doesn't bsg support sg v3 commands?
You should know, the discussion on that happened at the storage summit
and on linux-scsi. It was decided to drop sg v3 support from bsg, and
only focus on making bsg the driver for sg v4 commands.
As you know, we already have dual paths for sg v3. For sg v4 we can get
rid of that pain, and just have a single driver for handling that.
--
Jens Axboe
prev parent reply other threads:[~2007-07-24 11:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 1:06 [PATCH] unexport sg v3 helper functions FUJITA Tomonori
2007-07-23 12:02 ` Jens Axboe
2007-07-24 3:37 ` Douglas Gilbert
2007-07-24 6:49 ` Jens Axboe
2007-07-24 11:23 ` Douglas Gilbert
2007-07-24 11:34 ` Jens Axboe [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=20070724113433.GR3287@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=dougg@torque.net \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-scsi@vger.kernel.org \
--cc=tomof@acm.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;
as well as URLs for NNTP newsgroup(s).