From: Bowers, AndrewX <andrewx.bowers@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next-queue v5 PATCH 1/7] i40e: Introduce devlink interface
Date: Mon, 30 Jan 2017 21:33:16 +0000 [thread overview]
Message-ID: <26D9FDECA4FBDD4AADA65D8E2FC68A4A0FA5D49C@ORSMSX104.amr.corp.intel.com> (raw)
In-Reply-To: <1485392057-3261-2-git-send-email-sridhar.samudrala@intel.com>
> -----Original Message-----
> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at lists.osuosl.org] On
> Behalf Of Sridhar Samudrala
> Sent: Wednesday, January 25, 2017 4:54 PM
> To: intel-wired-lan at lists.osuosl.org
> Subject: [Intel-wired-lan] [next-queue v5 PATCH 1/7] i40e: Introduce devlink
> interface
>
> Add initial devlink support to get/set the mode of SRIOV switch.
> This patch sets the default mode as 'legacy' and enables getting the mode
> and and setting it to 'legacy'.
>
> The switch mode can be get/set via following 'devlink' commands.
>
> # devlink dev eswitch show pci/0000:05:00.0
> pci/0000:05:00.0: mode legacy
> # devlink dev eswitch set pci/0000:05:00.0 mode switchdev devlink answers:
> Operation not supported # devlink dev eswitch set pci/0000:05:00.0 mode
> legacy # devlink dev eswitch show pci/0000:05:00.0
> pci/0000:05:00.0: mode legacy
>
> Signed-off-by: Sridhar Samudrala <sridhar.samudrala@intel.com>
> Signed-off-by: Anjali Singhai <anjali.singhai@intel.com>
> ---
> drivers/net/ethernet/intel/Kconfig | 1 +
> drivers/net/ethernet/intel/i40e/i40e.h | 3 ++
> drivers/net/ethernet/intel/i40e/i40e_main.c | 80
> ++++++++++++++++++++++++++---
> 3 files changed, 76 insertions(+), 8 deletions(-)
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
next prev parent reply other threads:[~2017-01-30 21:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 0:54 [Intel-wired-lan] [next-queue v5 PATCH 0/7] i40e: Add VF Port Representator support for SR-IOV VFs Sridhar Samudrala
2017-01-26 0:54 ` [Intel-wired-lan] [next-queue v5 PATCH 1/7] i40e: Introduce devlink interface Sridhar Samudrala
2017-01-30 21:33 ` Bowers, AndrewX [this message]
2017-01-26 0:54 ` [Intel-wired-lan] [next-queue v5 PATCH 2/7] i40e: Introduce VF Port Representator(VFPR) netdevs Sridhar Samudrala
2017-01-30 21:33 ` Bowers, AndrewX
2017-02-01 1:06 ` Keller, Jacob E
2017-01-26 0:54 ` [Intel-wired-lan] [next-queue v5 PATCH 3/7] i40e: Sync link state between VFs and VFPRs Sridhar Samudrala
2017-01-30 21:34 ` Bowers, AndrewX
2017-01-26 0:54 ` [Intel-wired-lan] [next-queue v5 PATCH 4/7] net: store port/representator id in metadata_dst Sridhar Samudrala
2017-01-30 21:36 ` Bowers, AndrewX
2017-01-26 0:54 ` [Intel-wired-lan] [next-queue v5 PATCH 5/7] i40e: Add TX and RX support in switchdev mode Sridhar Samudrala
2017-01-30 21:34 ` Bowers, AndrewX
2017-02-15 15:59 ` Alexander Duyck
2017-02-15 17:37 ` Samudrala, Sridhar
2017-02-15 17:51 ` Alexander Duyck
2017-01-26 0:54 ` [Intel-wired-lan] [next-queue v5 PATCH 6/7] i40e: Add support for exposing VF port statistics via VFPR netdev on the host Sridhar Samudrala
2017-01-30 21:35 ` Bowers, AndrewX
2017-02-01 1:05 ` Keller, Jacob E
2017-02-01 18:21 ` Keller, Jacob E
2017-01-26 0:54 ` [Intel-wired-lan] [next-queue v5 PATCH 7/7] i40e: Add support to get switch id and port number for VFPR netdevs Sridhar Samudrala
2017-01-30 21:35 ` 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=26D9FDECA4FBDD4AADA65D8E2FC68A4A0FA5D49C@ORSMSX104.amr.corp.intel.com \
--to=andrewx.bowers@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 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.