From: Samudrala, Sridhar <sridhar.samudrala@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [net-next PATCH 5/6] i40e: Add TX and RX support in switchdev mode.
Date: Thu, 05 Jan 2017 14:32:54 -0800 [thread overview]
Message-ID: <586EC996.9080205@intel.com> (raw)
In-Reply-To: <CAJ3xEMgAaXNbvaP0=GcuTsVOOGwPHuSMQf-SeLKpxB8WrbEvng@mail.gmail.com>
On 1/5/2017 3:50 AM, Or Gerlitz wrote:
> On Thu, Jan 5, 2017 at 12:46 AM, Samudrala, Sridhar
> <sridhar.samudrala@intel.com> wrote:
>>
>> On 1/3/2017 3:03 PM, Or Gerlitz wrote:
>>> On Fri, Dec 30, 2016 at 7:04 PM, Samudrala, Sridhar
>>> <sridhar.samudrala@intel.com> wrote:
>>>> On 12/30/2016 7:31 AM, Or Gerlitz wrote:
>>>>> Are you exposing switchdev ops for the representators? didn't see that
>>>>> or maybe it's in the 4th patch which didn't make it to the list?
>>>> Not at this time. In the future patches when we offload fdb/vlan
>>>> functionality, we could use switchdev ops.
>>> but wait, this is the switchdev mode... even before doing any
>>> offloading, you want (need) your representor netdevices to have the
>>> same HW ID marking they are all ports of the same ASIC, this you can
>>> do with the switchdev parent ID attribute.
>> OK. I will add switchdev_port_attr_get() with PORT_PARENT_ID support in v3.
> Good, I made this comment, b/c we want to create a well defined user-experience
> to be taken into account also by upper virtualization layers.
>
> Another piece there to add is have your VF reps implement the
> get_phys_port_name ndo,
It looks like you are returning the VF port number as phys_port_name()
for a VF rep in en_rep.c.
Is this correct?
By default i am creating VFPR netdev with name as <pf_name>_VF<vf_num>
For ex; if enp5s0f0 is the pf name, VFPR netdev for VF0 will be enp5s0f0_vf0
If we want udev to follow this syntax should i return '_vf0' as
get_phys_port_name() for VF rep 0?
> where as we explain in commit cb67b832921cfa20ad79bafdc51f1745339d0557 is used
> as follows:
>
> Port phys name (ndo_get_phys_port_name) is implemented to allow exporting
> to user-space the VF vport number and along with the switchdev port parent
> id (phys_switch_id) enable a udev base consistent naming scheme:
>
> SUBSYSTEM=="net", ACTION=="add", ATTR{phys_switch_id}=="<phys_switch_id>", \
> ATTR{phys_port_name}!="", NAME="$PF_NIC$attr{phys_port_name}"
>
> where phys_switch_id is exposed by the PF (and VF reps) and $PF_NIC is
> the name of the PF netdevice.
>
> Or.
WARNING: multiple messages have this Message-ID (diff)
From: "Samudrala, Sridhar" <sridhar.samudrala@intel.com>
To: Or Gerlitz <gerlitz.or@gmail.com>
Cc: Alexander Duyck <alexander.h.duyck@intel.com>,
John Fastabend <john.r.fastabend@intel.com>,
Anjali Singhai Jain <anjali.singhai@intel.com>,
jakub.kicinski@netronome.com, intel-wired-lan@lists.osuosl.org,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [net-next PATCH 5/6] i40e: Add TX and RX support in switchdev mode.
Date: Thu, 05 Jan 2017 14:32:54 -0800 [thread overview]
Message-ID: <586EC996.9080205@intel.com> (raw)
In-Reply-To: <CAJ3xEMgAaXNbvaP0=GcuTsVOOGwPHuSMQf-SeLKpxB8WrbEvng@mail.gmail.com>
On 1/5/2017 3:50 AM, Or Gerlitz wrote:
> On Thu, Jan 5, 2017 at 12:46 AM, Samudrala, Sridhar
> <sridhar.samudrala@intel.com> wrote:
>>
>> On 1/3/2017 3:03 PM, Or Gerlitz wrote:
>>> On Fri, Dec 30, 2016 at 7:04 PM, Samudrala, Sridhar
>>> <sridhar.samudrala@intel.com> wrote:
>>>> On 12/30/2016 7:31 AM, Or Gerlitz wrote:
>>>>> Are you exposing switchdev ops for the representators? didn't see that
>>>>> or maybe it's in the 4th patch which didn't make it to the list?
>>>> Not at this time. In the future patches when we offload fdb/vlan
>>>> functionality, we could use switchdev ops.
>>> but wait, this is the switchdev mode... even before doing any
>>> offloading, you want (need) your representor netdevices to have the
>>> same HW ID marking they are all ports of the same ASIC, this you can
>>> do with the switchdev parent ID attribute.
>> OK. I will add switchdev_port_attr_get() with PORT_PARENT_ID support in v3.
> Good, I made this comment, b/c we want to create a well defined user-experience
> to be taken into account also by upper virtualization layers.
>
> Another piece there to add is have your VF reps implement the
> get_phys_port_name ndo,
It looks like you are returning the VF port number as phys_port_name()
for a VF rep in en_rep.c.
Is this correct?
By default i am creating VFPR netdev with name as <pf_name>_VF<vf_num>
For ex; if enp5s0f0 is the pf name, VFPR netdev for VF0 will be enp5s0f0_vf0
If we want udev to follow this syntax should i return '_vf0' as
get_phys_port_name() for VF rep 0?
> where as we explain in commit cb67b832921cfa20ad79bafdc51f1745339d0557 is used
> as follows:
>
> Port phys name (ndo_get_phys_port_name) is implemented to allow exporting
> to user-space the VF vport number and along with the switchdev port parent
> id (phys_switch_id) enable a udev base consistent naming scheme:
>
> SUBSYSTEM=="net", ACTION=="add", ATTR{phys_switch_id}=="<phys_switch_id>", \
> ATTR{phys_port_name}!="", NAME="$PF_NIC$attr{phys_port_name}"
>
> where phys_switch_id is exposed by the PF (and VF reps) and $PF_NIC is
> the name of the PF netdevice.
>
> Or.
next prev parent reply other threads:[~2017-01-05 22:32 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 6:20 [Intel-wired-lan] [net-next PATCH 0/6] i40e: Add VF port representator support or SR-IOV VFs Sridhar Samudrala
2016-12-30 6:20 ` Sridhar Samudrala
2016-12-30 2:53 ` [Intel-wired-lan] " David Miller
2016-12-30 2:53 ` David Miller
2016-12-30 16:55 ` [Intel-wired-lan] " Samudrala, Sridhar
2016-12-30 16:55 ` Samudrala, Sridhar
2016-12-30 6:20 ` [Intel-wired-lan] [net-next PATCH 1/6] i40e: Introduce devlink interface Sridhar Samudrala
2016-12-30 6:20 ` Sridhar Samudrala
2016-12-30 6:20 ` [Intel-wired-lan] [net-next PATCH 2/6] i40e: Introduce VF Port Representator(VFPR) netdevs Sridhar Samudrala
2016-12-30 6:20 ` Sridhar Samudrala
2016-12-30 2:52 ` [Intel-wired-lan] " David Miller
2016-12-30 2:52 ` David Miller
2016-12-30 6:21 ` [Intel-wired-lan] [net-next PATCH 3/6] i40e: Sync link state between VFs and VFPRs Sridhar Samudrala
2016-12-30 6:21 ` Sridhar Samudrala
2016-12-30 15:43 ` [Intel-wired-lan] " Or Gerlitz
2016-12-30 15:43 ` Or Gerlitz
2016-12-30 17:10 ` [Intel-wired-lan] " Samudrala, Sridhar
2016-12-30 17:10 ` Samudrala, Sridhar
2016-12-30 6:21 ` [Intel-wired-lan] [net-next PATCH 4/6] net: store port/representator id in metadata_dst Sridhar Samudrala
2016-12-30 6:21 ` [Intel-wired-lan] [net-next PATCH 5/6] i40e: Add TX and RX support in switchdev mode Sridhar Samudrala
2016-12-30 6:21 ` Sridhar Samudrala
2016-12-30 15:31 ` [Intel-wired-lan] " Or Gerlitz
2016-12-30 15:31 ` Or Gerlitz
2016-12-30 17:04 ` [Intel-wired-lan] " Samudrala, Sridhar
2016-12-30 17:04 ` Samudrala, Sridhar
2017-01-03 23:03 ` [Intel-wired-lan] " Or Gerlitz
2017-01-03 23:03 ` Or Gerlitz
2017-01-04 22:46 ` [Intel-wired-lan] " Samudrala, Sridhar
2017-01-04 22:46 ` Samudrala, Sridhar
2017-01-05 11:50 ` [Intel-wired-lan] " Or Gerlitz
2017-01-05 11:50 ` Or Gerlitz
2017-01-05 22:32 ` Samudrala, Sridhar [this message]
2017-01-05 22:32 ` Samudrala, Sridhar
2017-01-06 9:09 ` [Intel-wired-lan] " Or Gerlitz
2017-01-06 9:24 ` Or Gerlitz
2017-01-06 9:24 ` Or Gerlitz
2016-12-30 6:21 ` [Intel-wired-lan] [net-next PATCH 6/6] i40e: Add support for exposing VF port statistics via VFPR netdev on the host Sridhar Samudrala
2016-12-30 6:21 ` Sridhar Samudrala
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=586EC996.9080205@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 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.