Hi, I have a question about struct idbm.
I want to know what the role of the structure in the codes of open-
iscsi initiator is.
While reading codes in iscsiadm.c, idbm.c, etc, I see that struct idbm
is passed to
many functions. However, I found that these functions do not use the
structure
very
Hi, I have a question about struct idbm.
I want to know what the role of the structure in the codes of
open-iscsi initiator.
While reading codes of iscsiadm.c, idbm.c, etc, I see that struct idbm
is passed to
many functions. However, I found that these functions do not use the structure
very
() in iscsid_login_reqs_wait(). I
modify some codes
so that iscsid_req_by_rec will output logs.
Please give me a feedback if any.
-- Yangkook Kim
Signed-off-by: Yangkook Kim yangkook...@gmail.com
---
--- a/usr/iscsiadm.c2009-11-12 06:22:10.0 +0900
+++ b/usr/iscsiadm.c2009-11-12 06:23:01.0
This patch adds some codes to output logs to reflect the return value
of iscsid_req_wait() for outputting logging.
Please give me a feedback if any.
-- Yangkook Kim
Signed-off-by: Yangkook Kim yangkook...@gmail.com
---
--- a/usr/util.c2009-11-12 06:22:10.0 +0900
+++ b/usr
Are you hitting the non async code path? Did you hit the
iscsid_req_by_rec call? How many targets or portals were you logging into?
No, I never hit iscsid_req_by_rec call. I was just reading the codes
of iscsiadm and thought that there is less consideration when calling
iscsid_req_by_rec() than
2) Are there plans in the future to have more than one connection per session?
I dont't think so. If you want to know the reason, read the thread
titled MC/S support
in open-iscsi mailing list.
Kim
2009/11/17, Pasi Kärkkäinen pa...@iki.fi:
On Mon, Nov 16, 2009 at 09:39:00PM -0500, Hoot,
development process of this and other
linux project.
2009/11/24, Mike Christie micha...@cs.wisc.edu:
Mike Christie wrote:
Yangkook Kim wrote:
Hi, Mike. Thank you for your patch.
I do not want to add a login log message to the iscsid_req_* functions
because they are generic and could be used
Hi,
I just wanted to report a small problem applying kernel/2.6.26_compat.patch and
provide an updated patch to fix the problem.
If you try to compile the source from current git master branch for
kernel-2.6.26,
you will encounter patch error.
Here is what I did.
bash-3.2$ git clone
Hi, you are back.
I think for your patch, you want to include open_iscsi_compat.h in it.
I included open_iscsi_compat.h and created a patch. Please check it.
I have a quetion about creating a patch agaist files in sub-directory.
I used git diff to output the patch, but each hunk of outputted
I posted similar message on other thread, but let me ask the same question
with diffrent tittle.
I want to make a kernel compat patch without kernel/ sub-directory.
I used git diff to output the patch, but each header of outputted
patch includes kernel/ sub-directory like below.
e.g
diff --git
Hi, Group,
I am wondering why we have /sys/class/iscsi_connection for iscsi connection
in sysfs filesystem.
I understand that the one or more iscsi connection form a single iscsi session
and, in this sense, iscsi connection subordinates to iscsi session.
Then, it more makes sense if we have
,
session-id, conn-id, session-id);
Does it fit you very natural? Is it only me to worry about it?
2010/1/7, Mike Christie micha...@cs.wisc.edu:
On 01/02/2010 01:56 PM, Yangkook Kim wrote:
Hi, Group,
I am wondering why we have /sys/class/iscsi_connection for iscsi
connection
in sysfs
Remember that clients (especially Linux) doe cache blocks
locally
Doesn't kernel refresh the read cache for blocks at some intervals?
If I make a new file on target locally, and waiting for sometime,
hitting read command like ls on initiator side will read data from
block device, not from
Remember that clients (especially Linux) doe cache blocks
locally
Doesn't kernel refresh the read cache for blocks at some intervals?
If I make a new file on target locally, and waiting for sometime,
hitting read command like ls on initiator side will read data from
block device, not from
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.
Hi, all.
I want to know how to compile iscsid with iscsi modules already built
into the kernel.
I built a kernel with the following options selected in .config so that
iscsi_tcp, libiscsi and scsi_transport_iscsi are built into the kernel.
CONFIG_ISCSI_TCP=y
I compiled iscsid
Hi, lkml list.
I'm from open-iscsi mailing list and want to know if somebody
already worked on a patch to export module information of
scsi_transport_iscsi module to sysfs when it is compiled
and built in kernel.
Digging through open-iscsi and lkml list, I found some discussions
about this issue
17 matches
Mail list logo