From: John Fastabend <john.r.fastabend@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "Nelson, Shannon" <shannon.nelson@intel.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"gospo@redhat.com" <gospo@redhat.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"sassmann@redhat.com" <sassmann@redhat.com>
Subject: Re: [E1000-devel] [net-next v4 7/8] i40e: sysfs and debugfs interfaces
Date: Thu, 05 Sep 2013 16:38:15 -0700 [thread overview]
Message-ID: <522915E7.8010308@intel.com> (raw)
In-Reply-To: <20130905113259.55ad2ad2@nehalam.linuxnetplumber.net>
On 9/5/2013 11:32 AM, Stephen Hemminger wrote:
[...]
>
> IMHO attributes are a nice way of handling the VSI attributes since they
> seem hardware specific. Not sure how to do the right thing with switching.
> Should it look like Macvlan, bridge, VXLAN, or something else.
I think if you add a new rtnl link type call it "VSI" then it looks very
similar to a macvlan which has been offloaded. Additionally you get all
the fdb and ndo ops that already exist for free.
I proposed something similar here,
http://comments.gmane.org/gmane.linux.network/237617
although as Ben pointed out I screwed up the implementation. I'll work
on updating this to submit when net-next opens again.
.John
next prev parent reply other threads:[~2013-09-05 23:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 23:17 [net-next v4 0/8][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2013-09-04 23:17 ` [net-next v4 1/7] i40e: main driver core Jeff Kirsher
2013-09-05 16:26 ` Stephen Hemminger
2013-09-05 17:59 ` Nelson, Shannon
2013-09-04 23:17 ` [net-next v4 2/8] i40e: transmit, receive, and napi Jeff Kirsher
2013-09-04 23:17 ` [net-next v4 3/8] i40e: driver ethtool core Jeff Kirsher
2013-09-04 23:17 ` [net-next v4 4/8] i40e: driver core headers Jeff Kirsher
2013-09-04 23:17 ` [net-next v4 5/8] i40e: implement virtual device interface Jeff Kirsher
2013-09-04 23:17 ` [net-next v4 6/8] i40e: init code and hardware support Jeff Kirsher
2013-09-04 23:17 ` [net-next v4 7/8] i40e: sysfs and debugfs interfaces Jeff Kirsher
2013-09-05 0:37 ` [E1000-devel] " Stephen Hemminger
2013-09-05 1:25 ` Nelson, Shannon
2013-09-05 3:19 ` David Miller
2013-09-05 4:08 ` Brandeburg, Jesse
2013-09-05 4:37 ` David Miller
2013-09-06 3:09 ` Nelson, Shannon
2013-09-05 4:55 ` Stephen Hemminger
2013-09-05 11:10 ` Bjørn Mork
2013-09-05 15:21 ` Stephen Hemminger
2013-09-05 17:53 ` Nelson, Shannon
2013-09-05 18:32 ` [E1000-devel] " Stephen Hemminger
2013-09-05 23:38 ` John Fastabend [this message]
2013-09-04 23:17 ` [net-next v4 8/8] i40e: include i40e in kernel proper Jeff Kirsher
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=522915E7.8010308@intel.com \
--to=john.r.fastabend@intel.com \
--cc=davem@davemloft.net \
--cc=e1000-devel@lists.sourceforge.net \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sassmann@redhat.com \
--cc=shannon.nelson@intel.com \
--cc=stephen@networkplumber.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).