linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@suse.de>
To: dgilbert@interlog.com
Cc: Hannes Reinecke <hare@suse.de>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [LSF/MM TOPIC] SCSI referrals support
Date: Thu, 20 Jan 2011 10:36:01 -0600	[thread overview]
Message-ID: <1295541361.3014.8.camel@mulgrave.site> (raw)
In-Reply-To: <4D385F69.5060209@interlog.com>

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



  reply	other threads:[~2011-01-20 16:36 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 [this message]
2011-01-23 11:25     ` Boaz Harrosh
2011-01-24  8:04       ` Hannes Reinecke
2011-01-24  9:17         ` Boaz Harrosh
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=1295541361.3014.8.camel@mulgrave.site \
    --to=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 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).