From: Jakub Kicinski <kuba@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH net-next 0/2] net: default_rps_mask follow-up
Date: Wed, 15 Feb 2023 11:29:54 -0800 [thread overview]
Message-ID: <20230215112954.7990caa5@kernel.org> (raw)
In-Reply-To: <cover.1676484775.git.pabeni@redhat.com>
On Wed, 15 Feb 2023 19:33:35 +0100 Paolo Abeni wrote:
> The first patch namespacify the setting: once proper isolation
> is in place in the main namespace, additional demux in the child
> namespaces will be redundant.
Would you mind spelling this out again for me? If I create a veth with
the peer in a netns, the local end will get one RPS mask and the netns
end will get a RPS mask from the netns. If the daemon is not aware of
having to configure RPS masks (which I believe was your use case) then
it won't set the default mask in the netns either.. so we assume veth
is first created and then moved, or we don't use veth, or I'm lost
completely?
next prev parent reply other threads:[~2023-02-15 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 18:33 [PATCH net-next 0/2] net: default_rps_mask follow-up Paolo Abeni
2023-02-15 18:33 ` [PATCH net-next 1/2] net: make default_rps_mask a per netns attribute Paolo Abeni
2023-02-16 13:06 ` kernel test robot
2023-02-15 18:33 ` [PATCH net-next 2/2] self-tests: more rps self tests Paolo Abeni
2023-02-15 19:29 ` Jakub Kicinski [this message]
2023-02-15 20:33 ` [PATCH net-next 0/2] net: default_rps_mask follow-up Paolo Abeni
2023-02-15 23:05 ` 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=20230215112954.7990caa5@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
/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).