From: Jakub Kicinski <kuba@kernel.org>
To: Ilya Maximets <i.maximets@ovn.org>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFE net-next] net: tun: 1000x speed up
Date: Fri, 21 Oct 2022 09:07:56 -0700 [thread overview]
Message-ID: <20221021090756.0ffa65ee@kernel.org> (raw)
In-Reply-To: <20221021114921.3705550-1-i.maximets@ovn.org>
On Fri, 21 Oct 2022 13:49:21 +0200 Ilya Maximets wrote:
> Bump the advertised speed to at least match the veth. 10Gbps also
> seems like a more or less fair assumption these days, even though
> CPUs can do more. Alternative might be to explicitly report UNKNOWN
> and let the application/user decide on a right value for them.
UNKOWN would seem more appropriate but at this point someone may depend
on the speed being populated so it could cause regressions, I fear :S
> Sorry for the clickbait subject line.
Nicely done, worked on me :)
next prev parent reply other threads:[~2022-10-21 16:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 11:49 [RFE net-next] net: tun: 1000x speed up Ilya Maximets
2022-10-21 11:50 ` Ilya Maximets
2022-10-21 16:07 ` Jakub Kicinski [this message]
2022-10-24 9:44 ` Nicolas Dichtel
2022-10-24 11:56 ` Ilya Maximets
2022-10-24 12:27 ` Nicolas Dichtel
2022-10-24 15:39 ` Ilya Maximets
2022-10-24 15:59 ` Antonio Quartulli
2022-10-24 17:48 ` Ilya Maximets
2022-10-25 22:16 ` Antonio Quartulli
2022-10-26 12:56 ` Ilya Maximets
2022-10-24 11:08 ` Pavel Machek
2022-10-24 11:14 ` Ilya Maximets
[not found] ` <CAA93jw6G85VNAbzEa9HQFyw6x1cmqR=LAVVJmGBHocEcjaxZzA@mail.gmail.com>
2022-10-26 13:13 ` Ilya Maximets
2022-10-31 17:09 ` Ilya Maximets
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=20221021090756.0ffa65ee@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=i.maximets@ovn.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).