public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Douglas Gilbert <dougg@torque.net>
Cc: Mike Anderson <andmike@us.ibm.com>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi sysfs update (scsi_debug 3/3)
Date: Fri, 8 Nov 2002 02:30:56 +0000	[thread overview]
Message-ID: <20021108023055.A18954@infradead.org> (raw)
In-Reply-To: <3DCAF8AA.4050701@torque.net>; from dougg@torque.net on Fri, Nov 08, 2002 at 10:35:06AM +1100

On Fri, Nov 08, 2002 at 10:35:06AM +1100, Douglas Gilbert wrote:
> BTW Is the 256 minors limit history yet in 2.5?

No.  but for blockdevices minors are basically meaningless now.

> Whither sg?? Well it has been my intention to put
> a functionally stripped down version of the sg_io_hdr
> interface in a mid level ioctl. It could overlay the
> current SCSI_IOCTL_SEND_COMMAND or be a new ioctl
> number.

Please use a new one one, overloading only creates confusion.

> that it is dreadful (making sg_header look good :-) ).
> However from an application point of view you are
> still going to have sd, sr or st in the way of what
> you are really trying to do. Then there are the odd
> ball devices: this week I came across a SCSI printer
> type device for the first time. It's a modern device
> build to hide its true purpose from OSes!
> 
> Rather than a free standing upper level device, sg
> could be seen as an adjunct to the mid level. There is
> no need to probe sg to find out whether it is interested
> in a newly attach scsi device - by definition it is
> (unless it has run out of resources).

Yupp.  What I was thinking about was not to remove the sg device
nodes and leaving only the ioctl functionality as part of other
device nodes but rather creating a sg node for every scsi device,
without it beeing a "real" upper layer driver.

  reply	other threads:[~2002-11-08  2:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-07  7:36 [PATCH] scsi sysfs update (base 1/3) Mike Anderson
2002-11-07  7:39 ` [PATCH] scsi sysfs update (upper 2/3) Mike Anderson
2002-11-07  7:42   ` [PATCH] scsi sysfs update (scsi_debug 3/3) Mike Anderson
2002-11-07 23:30     ` Christoph Hellwig
2002-11-07 16:33       ` Mike Anderson
2002-11-07 23:35         ` Douglas Gilbert
2002-11-08  2:30           ` Christoph Hellwig [this message]
2002-11-07 23:29   ` [PATCH] scsi sysfs update (upper 2/3) Christoph Hellwig
2002-11-07 16:41     ` Mike Anderson
2002-11-08  1:20       ` Christoph Hellwig
2002-11-08  2:21         ` Mike Anderson
2002-11-08  3:34           ` Douglas Gilbert
2002-11-08  4:13             ` Mike Anderson
2002-11-08  4:53           ` Christoph Hellwig
2002-11-08  5:41             ` Mike Anderson
2002-11-07 23:28 ` [PATCH] scsi sysfs update (base 1/3) Christoph Hellwig
2002-11-07 17:01   ` Mike Anderson
2002-11-07 17:22     ` Patrick Mansfield

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=20021108023055.A18954@infradead.org \
    --to=hch@infradead.org \
    --cc=andmike@us.ibm.com \
    --cc=dougg@torque.net \
    --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