From: Alexander Duyck <alexander.duyck@gmail.com>
To: Or Gerlitz <ogerlitz@voltaire.com>
Cc: Alexander Duyck <alexander.h.duyck@intel.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"Fischer, Anna" <anna.fischer@hp.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Stephen Hemminger <shemminger@linux-foundation.org>
Subject: Re: L2 switching in igb
Date: Mon, 14 Sep 2009 19:52:48 -0700 [thread overview]
Message-ID: <5f2db9d90909141952r7ee9a4aj1d5e0dcdbceba111@mail.gmail.com> (raw)
In-Reply-To: <4AAE14CC.2000609@voltaire.com>
On Mon, Sep 14, 2009 at 3:02 AM, Or Gerlitz <ogerlitz@voltaire.com> wrote:
> To have VEPA support another bit has to be programmed... its the one that
> doesn't let the PF to forward a packet to a VF whose source mac matches the
> one in the packet (e.g multicast sender).
The bit I was referring to not setting would handle that. By
disabling the DTXSWC local loopback bit the PF will not send anything
to the VFs or visa versa.
> Yes, lets do that. I'd like to suggest that a "VF programmable from user
> space" context will contain a <mac, vlan-id, priority-bits, rate> tuple,
> such that in the absence of vlan tag, the VF driver will "sign" the packet
> (skb) with vlan-id and priority-bits assigned by the admin and the PF NIC
> will mandate that the VF originated traffic will not exceed the rate.
Well whenever I can get to it I will try to add that support. In the
meantime I believe there is a BOF session covering "Virtual Ethernet
switch enhancements and configuration" at the Linux Plumbers Conf that
will cover some of this so hopefully we can come up with a solid plan
on how to address this.
Thanks,
Alex
next prev parent reply other threads:[~2009-09-15 2:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 9:16 L2 switching in igb Or Gerlitz
2009-09-04 4:35 ` Alexander Duyck
2009-09-10 8:04 ` Or Gerlitz
2009-09-10 17:30 ` Alexander Duyck
2009-09-14 10:02 ` Or Gerlitz
2009-09-15 2:52 ` Alexander Duyck [this message]
2009-09-15 13:19 ` Or Gerlitz
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=5f2db9d90909141952r7ee9a4aj1d5e0dcdbceba111@mail.gmail.com \
--to=alexander.duyck@gmail.com \
--cc=alexander.h.duyck@intel.com \
--cc=anna.fischer@hp.com \
--cc=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@voltaire.com \
--cc=shemminger@linux-foundation.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).