netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: James Yonan <james@openvpn.net>
Cc: netdev@vger.kernel.org, therbert@google.com, stephen@networkplumber.org
Subject: Re: [PATCH net-next v2] rfs: added /proc/sys/net/core/rps_allow_ooo flag to tweak flow alg
Date: Mon, 11 Jul 2022 13:44:47 -0700	[thread overview]
Message-ID: <20220711134447.51162fd5@kernel.org> (raw)
In-Reply-To: <b84863e7-5acc-697c-0e08-af88b691e678@openvpn.net>

On Mon, 11 Jul 2022 14:38:39 -0600 James Yonan wrote:
> Any further questions/comments about this patch?  The v2 patch 
> incorporates all feedback received so far, including refactoring a large 
> conditional in the original code to make it more readable and maintainable.

There was another patch on the list doing a very similar thing right
around the time you posted yours. IIUC wireguard implements farming 
out decryption to multiple cores, implementing something in the tunnel
layer seems better. You can do the crypto in process context which is
much more efficient while at it, and put the packets back in order.

  reply	other threads:[~2022-07-11 20:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 16:54 [PATCH net-next] rfs: added /proc/sys/net/core/rps_allow_ooo flag to tweak flow alg James Yonan
2022-06-24 17:05 ` Stephen Hemminger
2022-06-28  5:17   ` [PATCH net-next v2] " James Yonan
2022-06-28 17:03     ` Jakub Kicinski
2022-06-28 23:49       ` James Yonan
2022-07-11 20:38         ` James Yonan
2022-07-11 20:44           ` Jakub Kicinski [this message]
2022-06-28 17:16     ` Jakub Kicinski

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=20220711134447.51162fd5@kernel.org \
    --to=kuba@kernel.org \
    --cc=james@openvpn.net \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    --cc=therbert@google.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).