public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: What's the state of sdev->tagged_queue
Date: Fri, 06 Jun 2003 10:28:15 -0400	[thread overview]
Message-ID: <3EE0A4FF.2020106@redhat.com> (raw)
In-Reply-To: <20030606141933.GA23096@lst.de>

Christoph Hellwig wrote:

> simple_tags == 1?  in my source it's a bitfield.

Duh, told you I was out of touch.  I wrote that and I forgot what it was :-)


>>Currently, we use the value of host->this_id to skip the scsi device of 
>>the host controller in our device scan.  What I would like to do is 
>>create an sg device entry for this_id that is type processor,
> 
> 
> We already have scsi_get_host_dev to get such a device if the LLDD
> wants it.  Generalizing it sounds like a good idea.  But before
> that we need a 64bit dev_t so we can have sg devices for the
> ever-growing number of scsi_devices :)
> 
> 
>>is a fake 
>>device, that implements whatever ioctls at the mid layer level that are 
>>appropriate, but that also allow the low level driver to register a fall 
>>through host ioctl routine that can be attached to this device.
> 
> 
> I don't think we should another ioctl routine.  Just use the normal
> ioctl routine in the host template and let the LLDD check for
> host->this_id.

More out-of-touchness...

-- 
   Doug Ledford <dledford@redhat.com>     919-754-3700 x44233
            Red Hat, Inc.
            1801 Varsity Dr.
            Raleigh, NC 27606



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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-06  7:48 What's the state of sdev->tagged_queue Christoph Hellwig
2003-06-06 14:04 ` Doug Ledford
2003-06-06 14:19   ` Christoph Hellwig
2003-06-06 14:28     ` Doug Ledford [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=3EE0A4FF.2020106@redhat.com \
    --to=dledford@redhat.com \
    --cc=hch@lst.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