From: Konrad Rzeszutek <konrad@darnok.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org, pjones@redhat.com,
konradr@redhat.com, konradr@linux.vnet.ibm.com
Subject: Re: [PATCH] Add iSCSI iBFT support.
Date: Wed, 26 Sep 2007 20:16:45 -0400 [thread overview]
Message-ID: <200709262016.47488.konrad@darnok.org> (raw)
In-Reply-To: <20070926141335.8faa5cb9.randy.dunlap@oracle.com>
>
> i.e., what is this binary blob (?)
>
> I don't see a binary blob in this patch (as stated in the first
> sentence). I'd say that this patch adds methods for exporting
> (or exposing) the ibft thru sysfs.
I used the wrong choice of words. The correct one is, as you say, to
add methods for exporting the iBFT through sysfs.
>
> Is there some good reason that the iSCSI connection information
> shouldn't be exposed in real sysfs attribute files instead of just
> in a binary file?
My end goal is to export the iBFT data via individual sysfs attribute files. I
was thinking to do that in the next version of this code and build on top of
this patch.
This way the existing exploiter (iscsi-initiator-utils) can use the parsing
code it already has to extract the data from the binary blob. Then in the
next version of the iscsi-initiator-utils (and for the kernel) I can post a
patch for supporting (and exporting in the kernel) individual sysfs attribute
files.
next prev parent reply other threads:[~2007-09-27 0:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 18:46 [PATCH] Add iSCSI iBFT support Konrad Rzeszutek
2007-09-26 19:37 ` roel
2007-09-26 21:10 ` Greg KH
2007-09-27 0:08 ` Konrad Rzeszutek
2007-09-27 2:04 ` Greg KH
2007-09-26 21:13 ` Randy Dunlap
2007-09-27 0:16 ` Konrad Rzeszutek [this message]
2007-09-26 21:29 ` Randy Dunlap
2007-09-27 0:52 ` Konrad Rzeszutek
[not found] ` <14e4363b0709261817t5f0b1922m99c24549ce316de8@mail.gmail.com>
2007-09-27 4:00 ` Randy Dunlap
2007-09-27 4:29 ` Randy Dunlap
2007-09-27 17:06 ` H. Peter Anvin
2007-09-27 17:12 ` Peter Jones
2007-09-27 17:18 ` H. Peter Anvin
2007-09-27 17:51 ` Peter Jones
2007-09-27 20:50 ` Len Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200709262016.47488.konrad@darnok.org \
--to=konrad@darnok.org \
--cc=konradr@linux.vnet.ibm.com \
--cc=konradr@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pjones@redhat.com \
--cc=randy.dunlap@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox