Mike Christie wrote:
On 03/15/2010 05:56 AM, Alex Zeffertt wrote:
The bugzilla ticket requests a merge of two git commits, but neither of
those contain the libiscsi.c change that addresses bug #2. Was this a
mistake, or did you deliberately omit that part of your
speed-up-conn-fail-take3.patch
Hi All,
Can someone explain about what is the usage of this print_scn_pdu()
function defined in isns.c file.
Thanks
Gopal.
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To post to this group, send email to open-is...@googlegroups.com.
To
Hi, all.
I'm now trying to study open-iscsi kernel space codes.
Basically my goal is understanding how iscsi packet
is created/sent/recieved in kernel space.
Unlike user space codes, there is no main function,
so not sure about where I should start from.
There are four kernel codes files.
iscsi_tcp.c if you are not a scsi guy already. Other wise
scsi_transport.cGood luck..
On Tue, Mar 16, 2010 at 8:52 PM, Yangkook Kim yangkook...@gmail.com wrote:
Hi, all.
I'm now trying to study open-iscsi kernel space codes.
Basically my goal is understanding how iscsi packet
is
On Mar 16, 2010, at 9:24 AM, Gopu Krishnan gopu.0...@gmail.com
wrote:
Hi All,
Can someone explain about what is the usage of this print_scn_pdu
() function defined in isns.c file.
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
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
On 03/16/2010 04:50 AM, Alex Zeffertt wrote:
Mike Christie wrote:
On 03/15/2010 05:56 AM, Alex Zeffertt wrote:
The bugzilla ticket requests a merge of two git commits, but neither of
those contain the libiscsi.c change that addresses bug #2. Was this a
mistake, or did you deliberately omit
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
On Mar 15, 4:53
On 03/16/2010 04:02 PM, bennyturns wrote:
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)
Thks Mike, that explains it :)
On Mar 16, 5:27 pm, Mike Christie micha...@cs.wisc.edu wrote:
On 03/16/2010 04:02 PM, bennyturns wrote:
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 +
10 matches
Mail list logo