All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Ming Zhang <mingz@ele.uri.edu>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: Re: about scsi_hostlist
Date: Sun, 17 Nov 2002 17:58:07 -0500	[thread overview]
Message-ID: <20021117225807.GK3280@redhat.com> (raw)
In-Reply-To: <200211172237.gAHMbF99022232@leviathan.ele.uri.edu>

On Sun, Nov 17, 2002 at 05:35:52PM -0500, Ming Zhang wrote: > Hi, Doug > >
For example, like the iSCSI target code, when it start, it should find all
SCSI disks or tapes link in order to export to client side. It need the
scsi_device pointer in order to send requests to it. That is why I need
it. Is there a formal way to find a scsi_device pointer by its lun, host
id, ... or by block layer major number and minor number?

There is a process by which it can be found, but it's too long to do on 
each command.  That means you need to hold a pointer to the device open 
to make this not be a performance slug.  What are you doing to hold a 
refcount on the devices you grab the pointer for so that they don't get 
freed without you knowing it?

P.S. - Enabling word wrap in your mailer would be most appreciated.

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

  parent reply	other threads:[~2002-11-17 22:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-17 22:35 Re: about scsi_hostlist Ming Zhang
2002-11-17 22:41 ` Christoph Hellwig
2002-11-17 22:58 ` Doug Ledford [this message]
2002-11-18  5:09 ` Oliver Xymoron
  -- strict thread matches above, loose matches on Subject: below --
2002-11-17 22:43 Ming Zhang
2002-11-17 23:03 Ming Zhang
2002-11-17 23:48 ` Alan Cox
2002-11-18  5:13   ` Oliver Xymoron

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=20021117225807.GK3280@redhat.com \
    --to=dledford@redhat.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mingz@ele.uri.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.