From: Jakub Kicinski <kuba@kernel.org>
To: Eric Dumazet <edumazet@google.com>
Cc: Albert Huang <huangjie.albert@bytedance.com>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Menglong Dong <imagedong@tencent.com>,
Petr Machata <petrm@nvidia.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
Antoine Tenart <atenart@kernel.org>, Phil Auld <pauld@redhat.com>,
Frederic Weisbecker <frederic@kernel.org>,
Xin Long <lucien.xin@gmail.com>, netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net : rps : supoort a single flow to use rps
Date: Tue, 28 Jun 2022 10:15:32 -0700 [thread overview]
Message-ID: <20220628101532.1be4a9df@kernel.org> (raw)
In-Reply-To: <CANn89iKfW8_OLN3veCaMDDLLPU1EP_eAcf03PJZJnLD+6Pv3vw@mail.gmail.com>
On Tue, 28 Jun 2022 17:31:12 +0200 Eric Dumazet wrote:
> > how to use:
> > echo xxx > /sys/class/net/xxx/queues/rx-x/rps_cpus
> > echo 1 > /sys/class/net/xxx/queues/rx-x/rps_single_flow
> > and create a flow node with the function:
> > rps_flow_node_create
>
> Which part calls rps_flow_node_create() exactly ?
>
> This seems to be very specialized to IPSEC.
>
> Can IPSEC use multiple threads for decryption ?
+1 Doesn't wireguard do something to spread the load across CPUs?
Maybe it can be generalized? I don't think a solution to "spray
crypto around" belongs as part of RPS.
prev parent reply other threads:[~2022-06-28 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 14:00 [PATCH] net : rps : supoort a single flow to use rps Albert Huang
2022-06-28 15:29 ` Alexander Lobakin
2022-06-29 9:09 ` David Laight
2022-06-28 15:31 ` Eric Dumazet
2022-06-28 17:15 ` Jakub Kicinski [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=20220628101532.1be4a9df@kernel.org \
--to=kuba@kernel.org \
--cc=arnd@arndb.de \
--cc=atenart@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=frederic@kernel.org \
--cc=huangjie.albert@bytedance.com \
--cc=imagedong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pauld@redhat.com \
--cc=petrm@nvidia.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 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.