From: Stephen Hemminger <shemminger@vyatta.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, Rakesh Ranjan <rakesh@chelsio.com>
Subject: Re: [RFC-PATCH] dhcp provisioning support in cxgb3i
Date: Wed, 4 Nov 2009 11:09:04 -0800 [thread overview]
Message-ID: <20091104110904.7ffc479b@s6510> (raw)
In-Reply-To: <4AF1C6C7.80103@chelsio.com>
On Wed, 04 Nov 2009 23:54:07 +0530
Rakesh Ranjan <rakesh@chelsio.com> wrote:
> Mike Christie wrote:
> > Rakesh Ranjan wrote:
> >> Mike Christie wrote:
> >>> 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.
> >>>
> >>> Is the idea to have iscsid/uip send down this msg?
> >>>
> >>> Was it not possible to hook in more like how bnx2i does dhcp?
> >>
> >> yep, idea is to have iscsid send down ISCSI_UEVENT_REQ_IPCONF msg.
> >> bnx2i approach in our case for at least T3 is not feasible.
> >>
> >
> > I think adding DHCP in the kernel is getting a little crazy :) If we go
> > down this path, I agree with the other person that stated it should at
> > least be generic.
>
> Hi Mike,
>
> What do you mean be generic ? Do you want to have a generic interface
> for DHCP handler that could be part of libiscsi and could be used by
> other LLD's.
Is there anyway to make existing code (in net/ipv4/ipconfig.c) more generic
and useful for both?
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Hemminger <shemminger@vyatta.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, Rakesh Ranjan <rakesh@chelsio.com>
Subject: Re: [RFC-PATCH] dhcp provisioning support in cxgb3i
Date: Wed, 4 Nov 2009 11:09:04 -0800 [thread overview]
Message-ID: <20091104110904.7ffc479b@s6510> (raw)
In-Reply-To: <4AF1C6C7.80103@chelsio.com>
On Wed, 04 Nov 2009 23:54:07 +0530
Rakesh Ranjan <rakesh@chelsio.com> wrote:
> Mike Christie wrote:
> > Rakesh Ranjan wrote:
> >> Mike Christie wrote:
> >>> 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.
> >>>
> >>> Is the idea to have iscsid/uip send down this msg?
> >>>
> >>> Was it not possible to hook in more like how bnx2i does dhcp?
> >>
> >> yep, idea is to have iscsid send down ISCSI_UEVENT_REQ_IPCONF msg.
> >> bnx2i approach in our case for at least T3 is not feasible.
> >>
> >
> > I think adding DHCP in the kernel is getting a little crazy :) If we go
> > down this path, I agree with the other person that stated it should at
> > least be generic.
>
> Hi Mike,
>
> What do you mean be generic ? Do you want to have a generic interface
> for DHCP handler that could be part of libiscsi and could be used by
> other LLD's.
Is there anyway to make existing code (in net/ipv4/ipconfig.c) more generic
and useful for both?
next prev parent reply other threads:[~2009-11-04 19:09 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
[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 [this message]
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=20091104110904.7ffc479b@s6510 \
--to=shemminger@vyatta.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.