From: Florian Fainelli <f.fainelli@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "Paweł Staszewski" <pstaszewski@itcare.pl>,
"Paolo Abeni" <pabeni@redhat.com>,
"Jesper Dangaard Brouer" <brouer@redhat.com>,
"Linux Kernel Network Developers" <netdev@vger.kernel.org>,
"Alexander Duyck" <alexander.duyck@gmail.com>
Subject: Re: Kernel 4.13.0-rc4-next-20170811 - IP Routing / Forwarding performance vs Core/RSS number / HT on
Date: Thu, 21 Sep 2017 15:07:11 -0700 [thread overview]
Message-ID: <7dbc2dd1-eec9-0bd3-7255-4fe6026847aa@gmail.com> (raw)
In-Reply-To: <1506030895.29839.153.camel@edumazet-glaptop3.roam.corp.google.com>
On 09/21/2017 02:54 PM, Eric Dumazet wrote:
> On Thu, 2017-09-21 at 14:41 -0700, Florian Fainelli wrote:
>
>> Would not this apply to pretty much any stacked device setup though? It
>> seems like any network device that just queues up its packet on another
>> physical device for actual transmission may need that (e.g: DSA, bond,
>> team, more.?)
>
> We support bonding and team already.
Right, so that seems to mostly leave us with DSA at least. What about
other devices that also have IFF_NO_QUEUE set?
--
Florian
next prev parent reply other threads:[~2017-09-21 22:07 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 17:51 Kernel 4.13.0-rc4-next-20170811 - IP Routing / Forwarding performance vs Core/RSS number / HT on Paweł Staszewski
2017-08-12 12:23 ` Jesper Dangaard Brouer
2017-08-12 17:27 ` Paweł Staszewski
2017-08-13 16:58 ` Paweł Staszewski
2017-08-14 16:19 ` Jesper Dangaard Brouer
2017-08-14 16:33 ` Eric Dumazet
2017-08-14 16:57 ` Paolo Abeni
2017-08-15 0:45 ` Paweł Staszewski
2017-08-15 1:07 ` Eric Dumazet
2017-08-15 1:17 ` Eric Dumazet
2017-08-15 9:11 ` Paweł Staszewski
2017-08-15 9:19 ` Paweł Staszewski
2017-08-15 10:05 ` Jesper Dangaard Brouer
2017-09-21 21:26 ` Paweł Staszewski
2017-09-21 21:34 ` Eric Dumazet
2017-09-21 21:34 ` Paweł Staszewski
2017-09-21 21:41 ` Florian Fainelli
2017-09-21 21:43 ` Paweł Staszewski
2017-09-21 21:54 ` Eric Dumazet
2017-09-21 22:07 ` Florian Fainelli [this message]
2017-09-22 0:37 ` Eric Dumazet
2017-10-18 21:49 ` Paweł Staszewski
2017-10-18 21:54 ` Eric Dumazet
2017-10-18 22:45 ` Paweł Staszewski
2017-09-09 9:03 ` Paweł Staszewski
2017-09-11 16:57 ` Paweł Staszewski
2017-09-11 22:11 ` Paweł Staszewski
2017-08-15 9:35 ` Jesper Dangaard Brouer
2017-08-15 0:38 ` Paweł Staszewski
2017-08-15 9:23 ` Jesper Dangaard Brouer
2017-08-15 9:30 ` Paweł Staszewski
2017-08-15 9:57 ` Jesper Dangaard Brouer
2017-08-15 10:02 ` Paweł Staszewski
2017-08-15 10:05 ` Paweł Staszewski
2017-08-15 10:28 ` Jesper Dangaard Brouer
2017-08-14 0:07 ` Alexander Duyck
2017-08-14 15:07 ` Paweł Staszewski
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=7dbc2dd1-eec9-0bd3-7255-4fe6026847aa@gmail.com \
--to=f.fainelli@gmail.com \
--cc=alexander.duyck@gmail.com \
--cc=brouer@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pstaszewski@itcare.pl \
/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.