open-iscsi Google Group

Re: [PATCH 2/2] RFC: The be2iscsi driver support for bsg

2010-03-18T21:02:52Z

I think this is what Jay is not trying to do. I think the patch has some
extra code like the ISCSI_BSG_HST_VENDOR parts that makes it confusing -
it got me too. The ISCSI_BSG_HST_VENDOR code in be2iscsi looks like it
is basically disabled (should remove for a formal patch when he sends
for merging).

Re: [PATCH 2/2] RFC: The be2iscsi driver support for bsg

2010-03-18T13:58:37Z

On Wed, 17 Mar 2010 23:37:07 +0530
So this patchset adds the user-kernel space interface for management
via bsg, right?
Then I have two questions.
- open-iscsi already has the user-kernel space interface for
management via netlink. Why do you need another via bsg? IOW, why
can't you do this via the existing netlink interface?

Re: [PATCH 1/2] RFC: Proposal for BSG Interface

2010-03-18T12:55:36Z

What? where? who? how? why? w*\? ...
You are proposing a new Kernel ABI/API here right. I think it is not acceptable
without a detailed documentation, including every little bit. Nothing missing.
If lots of it is already written for FC then grate most of your job is done.
But for us mortals please put some text on an introductory message. I use iscsi

Fwd: target creation and isns scn notification

2010-03-18T05:10:38Z

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 ----------
To: open-iscsi@googlegroups.com
Hi All,
In IET code, we create the target before the isns init. I understand that

[PATCH 2/2] RFC: The be2iscsi driver support for bsg

2010-03-17T18:07:07Z

This patch contains the necessary changes to support
the bsg interface
Signed-off-by: Jayamohan Kallickal <jayamoh...@serverengines.com>
---
drivers/scsi/be2iscsi/be_cmds. h | 137 ++++++++++++++++++++---
drivers/scsi/be2iscsi/be_iscsi .c | 3 +-
drivers/scsi/be2iscsi/be_main. c | 99 ++++++++++++++--

[PATCH 1/2] RFC: Proposal for BSG Interface

2010-03-17T18:06:09Z

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 <james.sm...@emulex.com>
Signed-off-by: Jayamohan Kallickal <jayamoh...@serverengines.com>
---
drivers/scsi/scsi_transport_is csi.c | 459 ++++++++++++++++++++++++++++++ ++++-

RFC: Proposal for BSG Interface

2010-03-17T18:05:14Z

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 <jayamoh...@serverengines.com>
---

target creation and isns scn notification

2010-03-17T10:24:56Z

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 SCN registration wont happen for targets

Re: x86 vs x86_64 and iSCSI

2010-03-17T09:21:33Z

"iSCSI backends" you mean iscsi-targets? Those machines that serve the
disks? Well that has nothing to do with open-iscsi. open-iscsi is the
initiator that sits on the filesystem side of the network.
For iscsi-targets you have 4 choices in Linux. IET, tgt, SCST, and LIO
not specifically in any order. Look up for each project's mailing-list

Re: Failover time of iSCSI multipath devices.

2010-03-16T21:53:55Z

Thks Mike, that explains it :)

Re: Failover time of iSCSI multipath devices.

2010-03-16T21:27:25Z

/sys/block/sdX/device/timeout is the scsi cmd timeout. It only comes
into play if you have nops off or have their timers set higher than the
scsi cmd timeout (you do not want to do this). When using nops if they
timeout then if the scsi cmd timer fires, the iscsi code would basically
tell the scsi layer they it is handling the problem so do not run the

Re: Failover time of iSCSI multipath devices.

2010-03-16T21:02:35Z

I am trying work out a formula for total failover time of my
multipathed iSCSI device so far I have:
failover time = nop timout + nop interval + replacement_timeout
seconds + scsi block device timeout(/sys/block/sdX/device/ timeout)
Is there anything else that I am missing?
-b

Re: Failover time of iSCSI multipath devices.

2010-03-16T17:47:09Z

I sent it to linux-scsi/James a couple days after I sent the patch in
this thread. It is not merged yet.
Do you want me to cc you on all future iscsi patches that go upstream?
When James merges it and sends it to linus, then I get a automated
message from him. If I cc you, you can get one too.

Re: [Iscsitarget-devel] iSNS implementation

2010-03-16T13:58:51Z

On Mar 16, 2010, at 9:24 AM, "Gopu Krishnan" <gopu.0...@gmail.com>
wrote:
You have the source code in front of you why don't you explain to me
what it does and if you see a problem point it out (CC the author of
that code too).
-Ross
______________________________ ______________________________ __________

x86 vs x86_64 and iSCSI

2010-03-16T16:36:23Z

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 driver? Does it matter at all? What are some factors that come