linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: [LSF/MM TOPIC] SCSI referrals support
Date: Thu, 20 Jan 2011 17:00:10 +0100	[thread overview]
Message-ID: <4D385C0A.3000901@suse.de> (raw)

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.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2011-01-20 15:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20 16:00 Hannes Reinecke [this message]
2011-01-20 16:14 ` [LSF/MM TOPIC] SCSI referrals support 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
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=4D385C0A.3000901@suse.de \
    --to=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).