From: Eric Dumazet <edumazet@google.com>
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: kuba@kernel.org, pabeni@redhat.com, davem@davemloft.net,
horms@kernel.org, netdev@vger.kernel.org,
Jason Xing <kernelxing@tencent.com>
Subject: Re: [PATCH net-next v2 2/3] net: rps: protect filter locklessly
Date: Wed, 17 Apr 2024 12:04:12 +0200 [thread overview]
Message-ID: <CANn89iLKxuBcriFNjtAS8DuhyLq2MPzGdvZxzijzhYdKM+Cw6w@mail.gmail.com> (raw)
In-Reply-To: <20240417062721.45652-3-kerneljasonxing@gmail.com>
On Wed, Apr 17, 2024 at 8:27 AM Jason Xing <kerneljasonxing@gmail.com> wrote:
>
> From: Jason Xing <kernelxing@tencent.com>
>
> As we can see, rflow->filter can be written/read concurrently, so
> lockless access is needed.
>
> Signed-off-by: Jason Xing <kernelxing@tencent.com>
> ---
> I'm not very sure if the READ_ONCE in set_rps_cpu() is useful. I
> scaned/checked the codes and found no lock can prevent multiple
> threads from calling set_rps_cpu() and handling the same flow
> simultaneously. The same question still exists in patch [3/3].
> ---
> net/core/dev.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/net/core/dev.c b/net/core/dev.c
> index 2003b9a61e40..40a535158e45 100644
> --- a/net/core/dev.c
> +++ b/net/core/dev.c
> @@ -4524,8 +4524,8 @@ set_rps_cpu(struct net_device *dev, struct sk_buff *skb,
> goto out;
> old_rflow = rflow;
> rflow = &flow_table->flows[flow_id];
> - rflow->filter = rc;
> - if (old_rflow->filter == rflow->filter)
> + WRITE_ONCE(rflow->filter, rc);
> + if (old_rflow->filter == READ_ONCE(rflow->filter))
You missed the obvious opportunity to use
if (old_rflow->filter == rc)
Here your code is going to force the compiler to read the memory right
after a prior write, adding a stall on some arches.
> old_rflow->filter = RPS_NO_FILTER;
> out:
> #endif
> @@ -4666,7 +4666,7 @@ bool rps_may_expire_flow(struct net_device *dev, u16 rxq_index,
> if (flow_table && flow_id <= flow_table->mask) {
> rflow = &flow_table->flows[flow_id];
> cpu = READ_ONCE(rflow->cpu);
> - if (rflow->filter == filter_id && cpu < nr_cpu_ids &&
> + if (READ_ONCE(rflow->filter) == filter_id && cpu < nr_cpu_ids &&
> ((int)(READ_ONCE(per_cpu(softnet_data, cpu).input_queue_head) -
> READ_ONCE(rflow->last_qtail)) <
> (int)(10 * flow_table->mask)))
> --
> 2.37.3
>
next prev parent reply other threads:[~2024-04-17 10:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 6:27 [PATCH net-next v2 0/3] locklessly protect left members in struct rps_dev_flow Jason Xing
2024-04-17 6:27 ` [PATCH net-next v2 1/3] net: rps: protect last_qtail with rps_input_queue_tail_save() helper Jason Xing
2024-04-17 6:27 ` [PATCH net-next v2 2/3] net: rps: protect filter locklessly Jason Xing
2024-04-17 10:04 ` Eric Dumazet [this message]
2024-04-17 11:03 ` Jason Xing
2024-04-17 11:52 ` Eric Dumazet
2024-04-17 11:58 ` Eric Dumazet
2024-04-17 12:14 ` Jason Xing
2024-04-17 12:20 ` Jason Xing
2024-04-17 6:27 ` [PATCH net-next v2 3/3] net: rps: locklessly access rflow->cpu Jason Xing
2024-04-17 12:24 ` Jason Xing
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=CANn89iLKxuBcriFNjtAS8DuhyLq2MPzGdvZxzijzhYdKM+Cw6w@mail.gmail.com \
--to=edumazet@google.com \
--cc=davem@davemloft.net \
--cc=horms@kernel.org \
--cc=kerneljasonxing@gmail.com \
--cc=kernelxing@tencent.com \
--cc=kuba@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).