All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luben Tuikov <tluben@rogers.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
	Mike Anderson <andmike@us.ibm.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH] make the SCSI mid-layer obey the device online flag
Date: Fri, 06 Jun 2003 11:28:22 -0400	[thread overview]
Message-ID: <3EE0B316.4060207@rogers.com> (raw)
In-Reply-To: <20030606073603.A13259@infradead.org>

Christoph Hellwig wrote:
> On Wed, Jun 04, 2003 at 03:14:56PM -0400, James Bottomley wrote:
> 
>>Yes, that's why I think forbidding *all* I/O after offlining is too much
>>effort.  Offlining should be a precursor to device destruction, but
>>actual destruction probably relys on detaching the queue from the block
>>device interface and sitting on it until all use counts drop to zero.
> 
> 
> We need a way to disable _all_ I/O to a device due to the way the driver
> model works.  The driver model ->remove always is a surprise removal,
> so the underlying PCI (or whatever) device for a scsi host can go away
> anytime.  Because of that we need to make damn sure no call to
> ->queuecommand will happen after scsi_remove_host is called.  Whether
> this is implemented with the same mechanisms as the current sdev->online
> is another question.

James was talking about ``device server not ready'' aliased to
online -- i.e. if online is 0 then only INQUIRY or TUR should
be sent from SCSI Core (unless SCSI Core decides to _know_ about
the different ULP).  The semantics on this are somewhat touched
in the INQUIRY description in SPC-3.

(This means that the device is on the SAN, but not ready to
process commands.)

You're talking about hardware removal -- more specifically
logical removal of a host -- in which case of course there's no
_host_, so how can online be checked.... (online being
member of sdev, sdev being parented by shost...)

IOW, you probably need either a flag in shost, to mean that
it's logically removed (whether hdwr or not) until it is
actually gone, or an external flag per host... it's your call.

-- 
Luben




  parent reply	other threads:[~2003-06-06 15:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-04 16:01 [PATCH] make the SCSI mid-layer obey the device online flag James Bottomley
2003-06-04 16:51 ` Mike Anderson
2003-06-04 19:14   ` James Bottomley
2003-06-05  0:34     ` Patrick Mansfield
2003-06-05 12:59       ` James Bottomley
2003-06-05 13:41       ` Alan Stern
2003-06-06  6:36     ` Christoph Hellwig
2003-06-06 15:19       ` James Bottomley
2003-06-06 15:51         ` Oliver Neukum
2003-06-06 16:02         ` Luben Tuikov
2003-06-06 15:28       ` Luben Tuikov [this message]
2003-06-06 15:39         ` James Bottomley
2003-06-06 15:52           ` Luben Tuikov
2003-06-06 16:04             ` James Bottomley
2003-06-06 20:51             ` Christoph Hellwig
2003-06-06 23:27               ` Luben Tuikov
2003-06-06 23:43                 ` James Bottomley
2003-06-07  5:20                   ` Luben Tuikov
2003-06-06 20:23         ` Mike Anderson
2003-06-06 20:52           ` Christoph Hellwig
2003-06-10  0:00           ` Mike Anderson
2003-06-06 20:49         ` Christoph Hellwig
2003-06-06 23:21           ` Luben Tuikov

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=3EE0B316.4060207@rogers.com \
    --to=tluben@rogers.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=andmike@us.ibm.com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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.