From: Chandra Seetharaman <sekharan@us.ibm.com>
To: Hannes Reinecke <hare@suse.de>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
dm-devel <dm-devel@redhat.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/7] scsi_dh: Implement generic device table handling
Date: Fri, 16 May 2008 11:32:59 -0700 [thread overview]
Message-ID: <1210962779.21974.330.camel@chandra-ubuntu> (raw)
In-Reply-To: <482BE368.3070506@suse.de>
On Thu, 2008-05-15 at 09:16 +0200, Hannes Reinecke wrote:
<snip>
>
> > On the other hand, if we could create a cache of the list of devices
> > (vendor-product-scsi_dh triplet) that has been attached, and walk
> > thru that list first before others during attach, it would help
> > (as we would guess there to be multiple of the same device).
> >
> Yes, but we can achieve that very same thing by walking the scsi_dh_list.
> I'll fix it up.
interested in seeing that.
<snip>
prev parent reply other threads:[~2008-05-16 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 14:43 [PATCH 1/7] scsi_dh: Implement generic device table handling Hannes Reinecke
2008-05-15 2:45 ` Chandra Seetharaman
2008-05-15 7:16 ` Hannes Reinecke
2008-05-16 18:32 ` Chandra Seetharaman [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=1210962779.21974.330.camel@chandra-ubuntu \
--to=sekharan@us.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dm-devel@redhat.com \
--cc=hare@suse.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