linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian King <brking@linux.vnet.ibm.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Hannes Reinecke <hare@suse.de>,
	Boaz Harrosh <bharrosh@panasas.com>,
	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: Thu, 31 Mar 2011 12:56:51 -0500	[thread overview]
Message-ID: <4D94C063.5030000@linux.vnet.ibm.com> (raw)
In-Reply-To: <AANLkTikL-EP=HsVjd_x9AmzptnrjSXdiNh3q1AriBz77@mail.gmail.com>

On 03/31/2011 11:40 AM, Bart Van Assche wrote:
> On Mon, Jan 24, 2011 at 9:04 AM, Hannes Reinecke <hare@suse.de> wrote:
>>
>> 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 :-)
>> - 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.
>>
>> 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.
> 
> (replying to an e-mail of two months ago)
> 
> There is another scenario where better unit attention support would
> help. Both the LIO-port and the SCST-port of the ibmvstgt driver
> suffer from the same race condition during reboot of the virtual I/O
> server (VIOS). Since the ibmvscsic driver reconnects to the ibmvscsis
> driver as soon as the ibmvscsis driver has been loaded the client
> reconnects before all LUNs have been configured in the VIOS system. So
> even if the target implementation generates an INQUIRY DATA HAS
> CHANGED unit attention condition for each LUN change, LUNs will have
> to be rescanned explicitly at the initiator side in order to get the
> initiator state in sync with the target state.

This sounds to me like the vscsi server drivers really need to change
to only register their CRQ and not initialize their CRQ until userspace has
setup all the target devices.

-Brian

-- 
Brian King
Linux on Power Virtualization
IBM Linux Technology Center



      reply	other threads:[~2011-03-31 17:56 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
2011-01-26 15:54           ` Hannes Reinecke
2011-03-31 16:40         ` Bart Van Assche
2011-03-31 17:56           ` Brian King [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=4D94C063.5030000@linux.vnet.ibm.com \
    --to=brking@linux.vnet.ibm.com \
    --cc=James.Bottomley@suse.de \
    --cc=bharrosh@panasas.com \
    --cc=bvanassche@acm.org \
    --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).