From: Greg KH <greg@kroah.com>
To: Konrad Rzeszutek <konrad@darnok.org>
Cc: Doug Maxey <dwm@enoyolf.org>,
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: Mon, 26 Nov 2007 21:28:47 -0800 [thread overview]
Message-ID: <20071127052847.GA777@kroah.com> (raw)
In-Reply-To: <200711262350.13100.konrad@darnok.org>
On Mon, Nov 26, 2007 at 11:50:10PM -0500, Konrad Rzeszutek wrote:
> > >
> > > sysfs files have ONE VALUE PER FILE, not a whole bunch of different
> > > things in a single file. Please fix this.
> >
> > The subparameters _are_ actually part of a single value, that value being
> > associated with the initiator instance.
> >
> > Konrad is trying to implement a "work-alike" for what open firmware does.
> > open-iscsi already has the ability to extract the same format
> > bits from real OFW.
> >
> > See open-iscsi.git/utils/fwparam_ppc.
>
>
> Greg,
>
> In light of what Doug says (which is all true), should I go ahead with a new
> version of this module which would export one value per file? The problem
> that will be encountered is that a ethernetX sysfs directory would have (for
> example):
>
> /sys/firmware/ibft/ethernet0/pci-bdf
> 5:1:0
> /sys/firmware/ibft/ethernet0/mac
> 00:11:25:9d:8b:00
> /sys/firmware/ibft/ethernet0/vlan
> 0
> /sys/firmware/ibft/ethernet0/gateway
> 192.168.79.254
> /sys/firmware/ibft/ethernet0/origin
> 0
> /sys/firmware/ibft/ethernet0/subnet-mask
> 22
> /sys/firmware/ibft/ethernet0/ip-addr
> 192.168.77.41
> /sys/firmware/ibft/ethernet0/flags
> 7
Yes, that is the proper way to do this kind of thing in sysfs.
> And the flag would contain the value "7" which would mean the user would have
> to parse what each bit means? (the v0.3 of the module does not export this
> flag but uses it to figure out which is the boot iSCSI target).
Sure, as long as it means something to userspace, and is a single value,
and is documented, that's fine.
thanks,
greg k-h
next prev parent reply other threads:[~2007-11-27 5:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 22:56 [PATCH] Add iSCSI IBFT Support (v0.3) 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 [this message]
2007-11-27 23:06 ` Arjan van de Ven
2007-11-29 15:36 ` darnok
2007-12-05 0:39 ` Konrad Rzeszutek
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=20071127052847.GA777@kroah.com \
--to=greg@kroah.com \
--cc=dwm@austin.ibm.com \
--cc=dwm@enoyolf.org \
--cc=hpa@zytor.com \
--cc=konrad@darnok.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.