All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: James.Smart@Emulex.Com
Cc: vst@vlnb.net, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 3/3] MidLayer updates - extending scsi_target support
Date: Sun, 6 Feb 2005 17:33:16 +0000	[thread overview]
Message-ID: <20050206173316.GA2589@infradead.org> (raw)
In-Reply-To: <0B1E13B586976742A7599D71A6AC733C12EB2A@xbl3.ma.emulex.com>

On Sun, Feb 06, 2005 at 12:28:17PM -0500, James.Smart@Emulex.Com wrote:
> Since the Emulex driver tracks things by target (actually FC remote port)
> rather than luns, having the ability to have driver data space in the
> lun didn't help much. Yes, the driver data space could be in the
> transport-specific FC remote port, but I thought a more generic solution
> would have been prefered - thus the patch request.
> 
> At this point, it appears that consensus is against the need for this,
> especially as it can be handled within the only area needed today - that of
> the FC transport.

Well, I disagree with that for certain.  I know of a handfull of SPI
HBA drivers that would benefit from per-target private data.


  reply	other threads:[~2005-02-06 17:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-06 17:28 [PATCH 3/3] MidLayer updates - extending scsi_target support James.Smart
2005-02-06 17:33 ` Christoph Hellwig [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-06  2:00 James.Smart
2005-02-05 15:04 James.Smart
2005-02-06  1:44 ` Douglas Gilbert
2005-01-29 14:03 James.Smart
2005-02-04 23:00 ` James Bottomley
2005-02-06 14:18 ` Vladislav Bolkhovitin
2005-05-24 17:06 ` 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=20050206173316.GA2589@infradead.org \
    --to=hch@infradead.org \
    --cc=James.Smart@Emulex.Com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=vst@vlnb.net \
    /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.