From: Scott Feldman <scofeldm@cisco.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>,
<chrisw@redhat.com>, Jens Osterkamp <Jens.Osterkamp@gmx.de>
Subject: Re: [net-next-2.6 PATCH 2/2] add ndo_set_port_profile op support for enic dynamic vnics
Date: Thu, 29 Apr 2010 09:31:38 -0700 [thread overview]
Message-ID: <C7FF027A.2CC04%scofeldm@cisco.com> (raw)
In-Reply-To: <201004291748.38702.arnd@arndb.de>
On 4/29/10 8:48 AM, "Arnd Bergmann" <arnd@arndb.de> wrote:
> I believe Chris is the one that was pushing most for having a single interface
> for both VDP/LLDPAD and enic.
> While I now understand your reasons for doing it in firmware and requiring the
> kernel interface in addition to the user interface, my doubts on whether VDP
> and your protocol should be part of the same interface are increasing.
>
> While I'm convinced that you can make it work for both now, the alternative
> to split the two may turn out to be cleaner. We'd still be able to do
> either of the two in kernel or user space. Using iproute2 syntax to describe
> this again, it would mean an interface like
>
> ip iov set port-profile DEVICE [ base BASE-DEVICE ] name PORT-PROFILE
> [ host_uuid HOST_UUID ]
> [ client_name CLIENT_NAME ]
> [ client_uuid CLIENT_UUID ]
> ip iov set vsi { associate | pre-associate | pre-associate-rr }
> BASE-DEVICE
> vsi MGR:VTID:VER
> mac LLADDR [ vlan VID ]
> client_uuid CLIENT_UUID
>
> ip iov del port_profile DEVICE [ base BASE-DEVICE ]
> ip iov del vsi BASE-DEVICE [ mac LLADDR [ vlan VID ] ]
> [ client_uuid CLIENT_UUID ]
>
> ip iov show port_profile DEVICE [ base BASE-DEVICE ]
> ip iov show vsi BASE-DEVICE [ mac LLADDR [ vlan VID ] ]
> [ client_uuid CLIENT_UUID ]
>
> You would obvioulsy only implement the kernel support for the port-profile
> stuff as callbacks, because no driver yet does VDP in the kernel, but we
> should
> have a common netlink header that defines both variants.
>
> Chris, any opinion on this interface as opposed to the combined one?
> Either one should work, but splitting it seems cleaner to me.
I'm OK with either version. Your latest does seem cleanest. Let's let
Chris be the final decider. Chris, door #1 or door #2?
-scott
next prev parent reply other threads:[~2010-04-30 17:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 4:42 [net-next-2.6 PATCH 1/2] Add netdev port-profile support (take III, was iovnl) Scott Feldman
2010-04-28 4:42 ` [net-next-2.6 PATCH 2/2] add ndo_set_port_profile op support for enic dynamic vnics Scott Feldman
2010-04-28 13:32 ` Arnd Bergmann
2010-04-28 18:39 ` Scott Feldman
2010-04-28 19:16 ` Arnd Bergmann
2010-04-28 22:38 ` Scott Feldman
2010-04-29 12:27 ` Arnd Bergmann
2010-04-29 14:32 ` Scott Feldman
2010-04-29 15:48 ` Arnd Bergmann
2010-04-29 16:31 ` Scott Feldman [this message]
2010-04-30 20:34 ` Scott Feldman
2010-05-01 12:36 ` Arnd Bergmann
2010-05-03 4:29 ` Vivek Kashyap
2010-05-03 11:32 ` Arnd Bergmann
2010-05-03 16:18 ` Vivek Kashyap
2010-04-28 13:13 ` [net-next-2.6 PATCH 1/2] Add netdev port-profile support (take III, was iovnl) Arnd Bergmann
2010-04-28 17:51 ` Scott Feldman
2010-04-28 19:33 ` Arnd Bergmann
2010-04-28 18:54 ` Scott Feldman
2010-04-28 19:37 ` Arnd Bergmann
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=C7FF027A.2CC04%scofeldm@cisco.com \
--to=scofeldm@cisco.com \
--cc=Jens.Osterkamp@gmx.de \
--cc=arnd@arndb.de \
--cc=chrisw@redhat.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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.