From: Boaz Harrosh <bharrosh@panasas.com>
To: Hannes Reinecke <hare@suse.de>
Cc: James Bottomley <James.Bottomley@suse.de>,
dgilbert@interlog.com,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [LSF/MM TOPIC] SCSI referrals support
Date: Mon, 24 Jan 2011 11:17:47 +0200 [thread overview]
Message-ID: <4D3D43BB.1060805@panasas.com> (raw)
In-Reply-To: <4D3D327F.1040807@suse.de>
On 01/24/2011 10:04 AM, Hannes Reinecke wrote:
> On 01/23/2011 12:25 PM, Boaz Harrosh wrote:
>> On 01/20/2011 06:36 PM, James Bottomley wrote:
>>> On Thu, 2011-01-20 at 17:14 +0100, Douglas Gilbert wrote:
>>>> On 11-01-20 05:00 PM, Hannes Reinecke wrote:
>>>>> Agenda topic proposal:
>>>>>
>>>>> SCSI referrals support has already been discussed at last year's LSF
>>>>> conference. However, the solution proposed there would not support
>>>>> failover and would require quite a lot of changes to multipathing.
>>>>>
>>>>> To enable failover it might be an idea to handle the LUN directly in
>>>>> multipathing. This would require eg:
>>>>> - request splitting
>>>>> - I/O alignment handling
>>>>> - SCSI unit attention handling
>>>>>
>>>>> I would be giving a short overview/presentation of the current
>>>>> state of the art, the shortcomings on the original proposal,
>>>>> and would like to invite a discussion on how to best support
>>>>> SCSI referrals.
>>>>
>>>> IMO a worrying aspect of the changes associated with SCSI
>>>> referrals is that sense data can now be returned with any
>>>> SCSI status (i.e. not just CHECK CONDITION). How well would
>>>> the SCSI subsystem cope with that? I know that the sg driver
>>>> (and probably bsg) would need changes, as would my libsgutils
>>>> library used by sg3_utils.
>>>
>>> Well, not necessarily. It scuppers plans to try to use the sense buffer
>>> more efficiently, but right at the moment, we can receive sense for any
>>> command. We only actually look at it on a check condition return, but
>>> that's easily updated.
>>>
>>> As I read the standard, referrals sense data on successfully completed
>>> commands is only really relevant to mp implementations, so it looks like
>>> the mid-layer should ignore it anyway (as it would now) but provide a
>>> hook for the device handlers to see it if they wanted.
>>>
>>> James
>>>
>> Something like:
>> diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c
>> index eafeeda..454e562 100644
>> --- a/drivers/scsi/scsi_lib.c
>> +++ b/drivers/scsi/scsi_lib.c
>> @@ -722,20 +722,23 @@ void scsi_io_completion(struct scsi_cmnd *cmd, unsigned int good_bytes)
>> sense_deferred = scsi_sense_is_deferred(&sshdr);
>> }
>>
>> + if (req->sense) {
>> + /*
>> + * SG_IO wants current and deferred errors
>> + */
>> + int len = 8 + cmd->sense_buffer[7];
>> +
>> + if (unlikely(len)) {
>> + if (len > SCSI_SENSE_BUFFERSIZE)
>> + len = SCSI_SENSE_BUFFERSIZE;
See here it will not crash
>> + memcpy(req->sense, cmd->sense_buffer, len);
>> + req->sense_len = len;
>> + }
>> + }
>> +
>> if (req->cmd_type == REQ_TYPE_BLOCK_PC) { /* SG_IO ioctl from block level */
>> req->errors = result;
>> if (result) {
>> - if (sense_valid && req->sense) {
>> - /*
>> - * SG_IO wants current and deferred errors
>> - */
>> - int len = 8 + cmd->sense_buffer[7];
>> -
>> - if (len > SCSI_SENSE_BUFFERSIZE)
>> - len = SCSI_SENSE_BUFFERSIZE;
>> - memcpy(req->sense, cmd->sense_buffer, len);
>> - req->sense_len = len;
>> - }
>> if (!sense_deferred)
>> error = -EIO;
>> }
>>
>> Then an interested user can just look at req->sense_len. The reset of the stack will
>> ignore all that because it looks for status/error-code.
>>
> Ah, if it were so easy. Currently sense codes have two problems:
>
> - They are limited to 96 bytes. Anything larger than that will just
> be discarded (or crash with your patch above :-)
It will not crash.
I have a patchset here that expands the request/scsi_cmnd sense_buffer
support to the maximum 260 bytes supported by the std.
If you want I can revive it. It is a sweep of all drivers, but a small
one, nothing like the accessors changes.
> - They inherit the same lifetime than the scsi command. But for any
> decent handling you really need to push them into some
> asynchronous context as you might well be within an interrupt
> handler here.
No that's fine. request->sense is a user supplied buffer that extends
the life of scsi_cmnd. above code just copies from a scsi-layer dma-able
buffer to the request->sense buffer. interrupt-time is fine.
> I'm currently working on a handling framework using relayfs
> (basically blktrace for SCSI Unit Attention); I can be doing a short
> presentation at LSF if requested.
>
That would be interesting. Thanks
> Cheers,
>
> Hannes
Boaz
next prev parent reply other threads:[~2011-01-24 9:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 16:00 [LSF/MM TOPIC] SCSI referrals support Hannes Reinecke
2011-01-20 16:14 ` Douglas Gilbert
2011-01-20 16:36 ` James Bottomley
2011-01-23 11:25 ` Boaz Harrosh
2011-01-24 8:04 ` Hannes Reinecke
2011-01-24 9:17 ` Boaz Harrosh [this message]
2011-01-26 15:54 ` Hannes Reinecke
2011-03-31 16:40 ` Bart Van Assche
2011-03-31 17:56 ` Brian King
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=4D3D43BB.1060805@panasas.com \
--to=bharrosh@panasas.com \
--cc=James.Bottomley@suse.de \
--cc=dgilbert@interlog.com \
--cc=hare@suse.de \
--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.