Hi All,
Can someone look into this issue as mentioned in the below mail thread.
I feel this is an BUG. If not please clarify on the same.
Thanks
Gopal.
-- Forwarded message --
From: Gopu Krishnan
Date: Wed, Mar 17, 2010 at 3:54 PM
Subject: target creation and isns scn notificati
This patch contains the necessary changes to support
the bsg interface
Signed-off-by: Jayamohan Kallickal
---
drivers/scsi/be2iscsi/be_cmds.h | 137 ---
drivers/scsi/be2iscsi/be_iscsi.c |3 +-
drivers/scsi/be2iscsi/be_main.c | 99 ++--
drivers/scsi/be2i
This patch contains the bsg interface based on
the bsg interface in FC.
Developed and submitted earlier by James Smart.
Signed-off-by: James Smart
Signed-off-by: Jayamohan Kallickal
---
drivers/scsi/scsi_transport_iscsi.c | 459 ++-
include/scsi/Kbuild
This submission contains an implementation of bsg interface
that is modelled on the FC BSG interface.
Also, contains the modified be2iscsi driver to support this interface.
These patches are made over the latest scsi-misc tree.
Signed-off-by: Jayamohan Kallickal
---
--
You receive
Hi All,
In IET code, we create the target before the isns init. I understand that
for per target we do have the isns scn registration. But we do SCN
registration only for the targets which are created by ietadm. From that
point is what the use_isns got enabled.
I would like to conclude, that the
On 03/16/2010 06:36 PM, dancho wrote:
> Hello,
>
> We are buying some recent 64-bit capable machines to serve as iSCSI
> backends to a file-server.
>
> I was wondering whether somebody has input on which architecture x86
> or x86_64 we should use for our iSCSI backends if we use the open-
> iscsi
