public inbox for linux-scsi@vger.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 19:27:45 -0400	[thread overview]
Message-ID: <3EE12371.90403@rogers.com> (raw)
In-Reply-To: <20030606215152.B3240@infradead.org>

Christoph Hellwig wrote:
> On Fri, Jun 06, 2003 at 11:52:56AM -0400, Luben Tuikov wrote:
> 
>>>Thus, we allow any special command because we assume it's part of error
>>>handling (or post error clean up).
>>
>>So SCSI Core _has_ decided to know about ULP (block, tape, optical).
>>
>>Unless we (SCSI Core) generate those, it's a pickle to decide
>>which are ``special'' enough commands.  I think that we'll see
>>more user space drivers controlling devices via sg sending
>>commands to the device for exactly those kinds of problems...
>>Else the burden on SCSI Core will/might be too great.
> 
> 
> I think James means REQ_SPECIAL request.  But some of them aren't
> special enough so we might need another flag for those.  But
> having knowledge about the upper drivers in the core sounds like
> a really bad idea.

*If* eh is to be done in SCSI Core you just cannot avoid it --
this is *the whole point* which James had in mind to allow
to send cmnds if !online. (see prev msgs on this thread)

(More things I want to mention here on this, but 1. No time
(I'm late for a meeting) and 2. I see no point -- you'll manage
just fine.)

-- 
Luben




  reply	other threads:[~2003-06-06 23: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
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 [this message]
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=3EE12371.90403@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox