.
-- james s
-Original Message-
From: Vladislav Bolkhovitin [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 06, 2005 9:18 AM
To: linux-scsi@vger.kernel.org
Cc: Smart, James
Subject: Re: [PATCH 3/3] MidLayer updates - extending scsi_target
support
Please, forgive me my ignorance
On Sun, Feb 06, 2005 at 12:28:17PM -0500, [EMAIL PROTECTED] 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
the idea behind this is fine, I just don't like the interface.
Really a target device is nothing more than a container to SCSI. We
already do the transport add/remove calls for targets, I don't see we
need other calls duplicating this. So, I think the
implementation would
look a whole
[EMAIL PROTECTED] wrote:
the idea behind this is fine, I just don't like the interface.
Really a target device is nothing more than a container to SCSI. We
already do the transport add/remove calls for targets, I don't see we
need other calls duplicating this. So, I think the
implementation
On Sat, 2005-01-29 at 09:03 -0500, [EMAIL PROTECTED] wrote:
This patch extends scsi_target support:
- Allows for driver-specific data to be allocated along with the
target structure and accessible via the starget-hostdata pointer.
- Adds scsi target alloc/configure/destory callbacks
Patch 3:
This patch extends scsi_target support:
- Allows for driver-specific data to be allocated along with the
target structure and accessible via the starget-hostdata pointer.
- Adds scsi target alloc/configure/destory callbacks to the
scsi host template.
- Rearranges the
6 matches
Mail list logo
