Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Shannon Nelson <shannon.nelson@oracle.com>,
	davem@davemloft.net, netdev@vger.kernel.org
Cc: silviu.smarandache@oracle.com
Subject: Re: [PATCH net-next] net: enable RPS on vlan devices
Date: Wed, 10 Oct 2018 11:32:48 -0700	[thread overview]
Message-ID: <78333418-4e54-8b58-288f-9b57e0054323@gmail.com> (raw)
In-Reply-To: <13b1a780-ebde-3f0c-65f3-72157bc23690@oracle.com>



On 10/10/2018 11:23 AM, Shannon Nelson wrote:
> For that matter, lots of features are "default off" until someone configures them, and there are lots of features that are only used by a subset of users.  In this case, we're trying to use something that already exists and arguably is broken for the vlan case.  Are there some technical reasons why this is not a good solution?

Simply code maintenance, and added cost for non vlan users.

Adding extra tests might help your use-case, but is slowing down other cases.

Since the need for new stuff will never end, really eBPF allow for arbitrary usage,
without the need for review kernel patches and maintaining it for next 10 years.

      reply	other threads:[~2018-10-11  1:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10  0:41 [PATCH net-next] net: enable RPS on vlan devices Shannon Nelson
2018-10-10  1:04 ` Eric Dumazet
2018-10-10  2:11   ` Shannon Nelson
2018-10-10  2:17     ` Eric Dumazet
2018-10-10 16:18       ` Shannon Nelson
2018-10-10 17:14         ` Eric Dumazet
2018-10-10 17:37           ` John Fastabend
2018-10-10 18:25             ` Shannon Nelson
2018-10-10 18:23           ` Shannon Nelson
2018-10-10 18:32             ` Eric Dumazet [this message]

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=78333418-4e54-8b58-288f-9b57e0054323@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=shannon.nelson@oracle.com \
    --cc=silviu.smarandache@oracle.com \
    /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