All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Fastabend <john.fastabend@gmail.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next PATCH 1/5] i40e: Introduce devlink interface.
Date: Wed, 10 Aug 2016 09:50:35 -0700	[thread overview]
Message-ID: <57AB5B5B.3090801@gmail.com> (raw)
In-Reply-To: <CAKgT0UeGtE2UUQWmjciz+zvLsCVPknvoUevmW6GRyDXMNCySSQ@mail.gmail.com>

On 16-08-10 09:01 AM, Alexander Duyck wrote:
> On Thu, Aug 4, 2016 at 9:49 AM, Sridhar Samudrala
> <sridhar.samudrala@intel.com> wrote:
>> Add initial devlink support to set/get the mode of SRIOV switch.
>> This patch allows the mode to be set to either 'legacy' or 'switchdev', but
>> doesn't implement any functionality to create vf representors in switchdev
>> mode.
>>
>> With smode support in iproute2 'devlink' utility, switch mode can be set
>> and get via following commands.
>>
>>     # devlink dev smode pci/0000:05:00.0
>>     mode: legacy
>>     # devlink dev set pci/0000:05:00.0 smode switchdev
>>     # devlink dev smode pci/0000:05:00.0
>>     mode: switchdev
>>
>> Signed-off-by: Sridhar Samudrala <sridhar.samudrala@intel.com>
> 
> I really don't see much value in this patch.  If you are going to
> support SwitchDev then just do it.  Otherwise you are adding extra
> overhead for maintaining two different modes.
> 
> I would recommend putting this series out to netdev as an RFC.
> Submitting it to intel-wired-lan is kind of pointless as the audience
> it to small to get any valuable review.
> 
> - Alex

I argued at length about this already. Jiri and company wanted this flag
to push device in and out of this mode. Here we are just following the
already upstreamed and debated decision.

This is less about switchdev and more about generating VF netdevs to
use with ip tools and friends.

Another option would be to just always enable VF netdevs and have no
legacy mode at all. I think that would be fine it just depends on if
you think having extra netdevs around will confuse the stack at all.
It might create a few corner cases but one reasonable thing to do
would be to just fix those cases as they appear.

Thanks,
John


  reply	other threads:[~2016-08-10 16:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04 16:49 [Intel-wired-lan] [next PATCH 1/5] i40e: Introduce devlink interface Sridhar Samudrala
2016-08-04 16:49 ` [Intel-wired-lan] [next PATCH 2/5] i40e: Introduce VF representor/control netdevs Sridhar Samudrala
2016-08-10  0:18   ` Nambiar, Amritha
2016-08-04 16:49 ` [Intel-wired-lan] [next PATCH 3/5] i40e: Enable VF specific ethtool statistics via VF representor netdevs Sridhar Samudrala
2016-08-10  0:21   ` Nambiar, Amritha
2016-08-04 16:49 ` [Intel-wired-lan] [next PATCH 4/5] i40e: Refactor flow director filter management to make it per VSI Sridhar Samudrala
2016-08-04 16:49 ` [Intel-wired-lan] [next PATCH 5/5] i40e: Enable ntuple filters on VFs via VF representor netdevs Sridhar Samudrala
2016-08-10  0:12 ` [Intel-wired-lan] [next PATCH 1/5] i40e: Introduce devlink interface Nambiar, Amritha
2016-08-10 16:01 ` Alexander Duyck
2016-08-10 16:50   ` John Fastabend [this message]
2016-08-10 18:18     ` Alexander Duyck
2016-08-10 18:41       ` John Fastabend
2016-08-16 18:54         ` Samudrala, Sridhar
2016-08-16 20:39           ` Alexander Duyck
2016-08-16 21:51             ` Samudrala, Sridhar
2016-08-17  0:17               ` Alexander Duyck
2016-08-17 19:24                 ` John Fastabend
2016-08-10 20:50 ` 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=57AB5B5B.3090801@gmail.com \
    --to=john.fastabend@gmail.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.