linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <openosd@gmail.com>
To: dgilbert@interlog.com,
	SCSI development list <linux-scsi@vger.kernel.org>,
	Christian Franke <Christian.Franke@t-online.de>,
	James Bottomley <james.bottomley@hansenpartnership.com>
Subject: Re: [PATCH v5] sg: relax 16 byte cdb restriction
Date: Thu, 05 Jun 2014 18:46:38 +0300	[thread overview]
Message-ID: <539090DE.7040808@gmail.com> (raw)
In-Reply-To: <53908F6A.5090309@gmail.com>

On 06/05/2014 06:40 PM, Boaz Harrosh wrote:
> On 06/03/2014 08:18 PM, Douglas Gilbert wrote:
>> v4 of this patch was sent 20131201.
>>
>> ChangeLog:
>>          - remove the 16 byte CDB (SCSI command) length limit
>>            from the sg driver by handling longer CDBs the same
>>            way as the bsg driver. Remove comment from sg.h
>>            public interface about the cmd_len field being
>>            limited to 16 bytes.
>>          - remove some dead code caused by this change
>>          - cleanup comment block at the top of sg.h, fix urls
>>
>> Signed-off-by: Douglas Gilbert <dgilbert@interlog.com>
>>
>>
>> sg_cdb_dg5.patch
>>
>>
> <>
>>  
>> +/* SG_MAX_CDB_SIZE should be 260 (spc4r37 section 3.1.30) however the type
>> + * of sg_io_hdr::cmd_len can only represent 255
>> + */
>> +#define SG_MAX_CDB_SIZE 255
>> +
<>

BTW here too. Why new code is using the old interface?
I thought that the all point for having bsg at all is
that new stuff are implemented there in a cleaner interface
for example large CDBs.
Otherwise what was the point for bsg in the first place?
(It was before my time, It would be nice to know?)

What is then left unique at bsg after this patch? only bidi?

Thanks
Boaz


  reply	other threads:[~2014-06-05 15:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-03 17:18 [PATCH v5] sg: relax 16 byte cdb restriction Douglas Gilbert
2014-06-05 13:02 ` Christoph Hellwig
2014-06-05 15:40 ` Boaz Harrosh
2014-06-05 15:46   ` Boaz Harrosh [this message]
2014-06-05 22:21   ` Douglas Gilbert
2014-06-11 21:37 ` Mike Christie

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=539090DE.7040808@gmail.com \
    --to=openosd@gmail.com \
    --cc=Christian.Franke@t-online.de \
    --cc=dgilbert@interlog.com \
    --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 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).