public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Martin Peschke3 <MPESCHKE@de.ibm.com>
Cc: Greg KH <greg@kroah.com>,
	Heiko Carstens <Heiko.Carstens@de.ibm.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	linux-scsi-owner@vger.kernel.org, Matthew Wilcox <matthew@wil.cx>,
	willy@www.linux.org.uk
Subject: Re: [PATCH] zfcp: updates for -bk
Date: Tue, 25 Jan 2005 12:40:07 -0600	[thread overview]
Message-ID: <1106678407.6434.43.camel@mulgrave> (raw)
In-Reply-To: <OF09208441.E1CA6752-ONC1256F94.005CDE81-C1256F94.00647837@de.ibm.com>

On Tue, 2005-01-25 at 19:10 +0100, Martin Peschke3 wrote:
> Actually, you will find the adapter structure be an anchor for several
> other objects, or lists of them respectively. We tried to organize
> all the driver private data in a sane way. That means there is a tree
> of objects representing the SAN topology, including target ports and
> subordinate LUNs, many of which have an associated mid-layer structure.
> I can't imagine that anybody would ever argue to collapse all that into
> the adapter structure. So, why all the fuss about this particular object?
> The generic services object has nothing to do with the adapter. It's about
> fabric switch services, or certain well-known FC (target) ports, which can
> be accessed in the fabric through an adapter. It's not local but remote,
> like other targets, so to speak. We might also have chosen to call it
> "fabric switch".

OK, take a look at this:

http://marc.theaimsgroup.com/?l=linux-scsi&m=110546207223304

and tell me if it does everything you need.  If it doesn't, you could
try adding all the other bits to the fc transport class.

James



  reply	other threads:[~2005-01-25 18:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-25 18:10 [PATCH] zfcp: updates for -bk Martin Peschke3
2005-01-25 18:40 ` James Bottomley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-24  9:46 Heiko Carstens
2005-01-24 14:22 ` Matthew Wilcox
2005-01-24 14:48   ` Heiko Carstens
2005-01-24 15:31     ` James Bottomley
2005-01-25  6:08       ` Heiko Carstens
2005-01-25 15:20         ` James Bottomley

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=1106678407.6434.43.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=Heiko.Carstens@de.ibm.com \
    --cc=MPESCHKE@de.ibm.com \
    --cc=greg@kroah.com \
    --cc=linux-scsi-owner@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=willy@www.linux.org.uk \
    /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