From: Konrad Rzeszutek <konrad@darnok.org>
To: darnok@68k.org
Cc: Arjan van de Ven <arjan@infradead.org>,
Doug Maxey <dwm@enoyolf.org>, Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org, pjones@redhat.com,
konradr@redhat.com, konradr@linux.vnet.ibm.com,
randy.dunlap@oracle.com, hpa@zytor.com, lenb@kernel.org,
mike.anderson@us.ibm.com, dwm@austin.ibm.com
Subject: Re: [PATCH] Add iSCSI IBFT Support (v0.3)
Date: Tue, 4 Dec 2007 20:39:25 -0400 [thread overview]
Message-ID: <20071205003925.GG6736@andromeda.dapyr.net> (raw)
In-Reply-To: <20071129153621.GA4669@andromeda.dapyr.net>
On Thu, Nov 29, 2007 at 11:36:21AM -0400, darnok@68k.org wrote:
> > >
> > > /sys/firmware/ibft/ethernet0/pci-bdf
> > > 5:1:0
> >
> > shouldn't this somehow also have a symlink to the kernels ethX view of
> > ethernet devices?
> > (and if so.. how much of the info is duplicated..)
>
> That NIC is used by the NIC firmware (or the BIOS) to negotiate
> the iSCSI target. The information that is in this directory is what
> the BIOS used (note past tense) which might very well be completly
> different from what Linux uses.
>
> My rationale behind _not_ linking to ethX view was that it could
> be confusing and not entirely useful for users: "It says that _this_
> NIC, with this IP, uses this iSCSI target. But Linux is using a
> completly different NIC (and IP) to setup a iSCSI connection to the
> same iSCSI target!?"
On the other hand having a link to the device and being able to
extra data sounds good too. I've made a modification and posted
a new version, under the 'REPORT [PATCH] Add iSCSI iBFT v0.4'.
Review would be much appreciated.
next prev parent reply other threads:[~2007-12-05 0:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 22:56 Konrad Rzeszutek
2007-11-26 23:53 ` Randy Dunlap
2007-11-27 4:23 ` Konrad Rzeszutek
2007-11-27 3:23 ` Greg KH
2007-11-27 3:31 ` Greg KH
2007-11-27 4:12 ` Doug Maxey
2007-11-27 4:50 ` Konrad Rzeszutek
2007-11-27 5:28 ` Greg KH
2007-11-27 23:06 ` Arjan van de Ven
2007-11-29 15:36 ` darnok
2007-12-05 0:39 ` Konrad Rzeszutek [this message]
2007-11-27 4:23 ` Konrad Rzeszutek
2007-11-27 5:29 ` Greg KH
2007-11-27 18:09 ` darnok
2007-11-27 19:09 ` Greg KH
2007-11-28 19:21 ` darnok
2007-11-28 19:45 ` Greg KH
2007-11-28 20:24 ` darnok
2007-11-28 20:33 ` Greg KH
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=20071205003925.GG6736@andromeda.dapyr.net \
--to=konrad@darnok.org \
--cc=arjan@infradead.org \
--cc=darnok@68k.org \
--cc=dwm@austin.ibm.com \
--cc=dwm@enoyolf.org \
--cc=greg@kroah.com \
--cc=hpa@zytor.com \
--cc=konradr@linux.vnet.ibm.com \
--cc=konradr@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.anderson@us.ibm.com \
--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
Powered by JetHome