From: Ben Hutchings <bhutchings@solarflare.com>
To: Rakesh Ranjan <rakesh@chelsio.com>
Cc: Mike Christie <michaelc@cs.wisc.edu>,
davem@davemloft.net, James Bottomley <James.Bottomley@suse.de>,
Karen Xie <kxie@chelsio.com>,
"open-iscsi@googlegroups.com" <open-iscsi@googlegroups.com>,
LKML <linux-kernel@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: [RFC-PATCH] dhcp provisioning support in cxgb3i
Date: Thu, 29 Oct 2009 14:06:54 +0000 [thread overview]
Message-ID: <1256825214.2827.10.camel@achroite> (raw)
In-Reply-To: <4AE995C4.4080909@chelsio.com>
On Thu, 2009-10-29 at 18:46 +0530, Rakesh Ranjan wrote:
> Hi Mike,
>
> Herein attached patches for having dhcp provisioning support in
> cxgb3i.
> I have added one new iscsi netlink message ISCSI_UEVENT_REQ_IPCONF.
> Please have a look and share suggestions.
[...]
Why does cxgb3i need its very own DHCP client? This seems like
something that's generically useful to firmware-based iSCSI adapters.
(It would be better still if this could be left to user-space, but
although a user-space program could send out requests on the net device
using the iSCSI device's MAC address, I don't see how it would get
replies.)
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2009-10-29 14:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 13:16 [RFC-PATCH] dhcp provisioning support in cxgb3i Rakesh Ranjan
2009-10-29 13:16 ` Rakesh Ranjan
2009-10-29 14:06 ` Ben Hutchings [this message]
[not found] ` <4AE995C4.4080909-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
2009-10-29 21:09 ` Mike Christie
2009-10-29 21:09 ` Mike Christie
2009-10-30 5:24 ` Rakesh Ranjan
2009-11-02 23:48 ` Mike Christie
2009-11-04 18:24 ` Rakesh Ranjan
2009-11-04 19:09 ` Stephen Hemminger
2009-11-04 19:09 ` Stephen Hemminger
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=1256825214.2827.10.camel@achroite \
--to=bhutchings@solarflare.com \
--cc=James.Bottomley@suse.de \
--cc=davem@davemloft.net \
--cc=kxie@chelsio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=netdev@vger.kernel.org \
--cc=open-iscsi@googlegroups.com \
--cc=rakesh@chelsio.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.