Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Samudrala, Sridhar <sridhar.samudrala@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next-queue v6 PATCH 2/7] i40e: Introduce Port Representor netdevs and switchdev mode.
Date: Mon, 3 Apr 2017 11:41:15 -0700	[thread overview]
Message-ID: <58E2974B.30503@intel.com> (raw)
In-Reply-To: <CAJ3xEMgVeri17KceKhnFUCCFj00yWXKtjwP4r36Pb-CSZiOTng@mail.gmail.com>



On 3/30/2017 12:17 AM, Or Gerlitz wrote:
> On Thu, Mar 30, 2017 at 3:22 AM, Sridhar Samudrala 
> <sridhar.samudrala at intel.com <mailto:sridhar.samudrala@intel.com>> wrote:
>
>     Port Representator netdevs are created for each PF and VF if the
>     switch
>     mode is set to 'switchdev'. These netdevs can be used to control and
>     configure VFs and PFs when they are moved to a different namespace.
>     They enable exposing statistics, configure and monitor link state,
>     mtu,
>     filters,fdb/vlan entries etc.
>
>
>
> What netdev represents the uplink (wire port) in your impl?
>
We don't have a port netdev representing the uplink in this 
implementation as we
cannot control the frames going out the uplink via sw rules with the 
current generation of
hw/fw.

-Sridhar

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20170403/b8a82103/attachment.html>

  reply	other threads:[~2017-04-03 18:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30  0:22 [Intel-wired-lan] [next-queue v6 PATCH 0/7] i40e: Add port representor and initial switchdev support Sridhar Samudrala
2017-03-30  0:22 ` [Intel-wired-lan] [next-queue v6 PATCH 1/7] i40e: Introduce devlink interface Sridhar Samudrala
2017-03-31 19:35   ` Bowers, AndrewX
2017-03-30  0:22 ` [Intel-wired-lan] [next-queue v6 PATCH 2/7] i40e: Introduce Port Representor netdevs and switchdev mode Sridhar Samudrala
2017-03-30  7:17   ` Or Gerlitz
2017-04-03 18:41     ` Samudrala, Sridhar [this message]
2017-04-04 11:58       ` Or Gerlitz
2017-04-04 15:29         ` Alexander Duyck
2017-04-05 13:41           ` Or Gerlitz
2017-03-30  9:17   ` Or Gerlitz
2017-03-31 19:35   ` Bowers, AndrewX
2017-03-30  0:22 ` [Intel-wired-lan] [next-queue v6 PATCH 3/7] i40e: Sync link state between PF/VFs and Port representor netdevs Sridhar Samudrala
2017-03-31 19:37   ` Bowers, AndrewX
2017-03-30  0:22 ` [Intel-wired-lan] [next-queue v6 PATCH 4/7] net: store port/representator id in metadata_dst Sridhar Samudrala
2017-03-31 19:42   ` Bowers, AndrewX
2017-03-30  0:22 ` [Intel-wired-lan] [next-queue v6 PATCH 5/7] i40e: Add TX and RX support over port netdev's in switchdev mode Sridhar Samudrala
2017-03-30  9:26   ` Or Gerlitz
2017-04-03 18:52     ` Samudrala, Sridhar
2017-04-14 16:47   ` Alexander Duyck
2017-04-14 18:26     ` Samudrala, Sridhar
2017-03-30  0:22 ` [Intel-wired-lan] [next-queue v6 PATCH 6/7] i40e: Add support for exposing switch port statistics via port netdevs Sridhar Samudrala
2017-03-31 19:39   ` Bowers, AndrewX
2017-03-30  0:22 ` [Intel-wired-lan] [next-queue v6 PATCH 7/7] i40e: Add support to get switch id and port number for " Sridhar Samudrala
2017-03-30 21:45   ` Jakub Kicinski
2017-03-30 22:31     ` Alexander Duyck
2017-03-31  1:16       ` Jakub Kicinski
2017-03-31 21:09   ` Bowers, AndrewX

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=58E2974B.30503@intel.com \
    --to=sridhar.samudrala@intel.com \
    --cc=intel-wired-lan@osuosl.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