From: Jason Xing <kerneljasonxing@gmail.com>
To: Eric Dumazet <edumazet@google.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 20:14:09 +0800 [thread overview]
Message-ID: <CAL+tcoCW2-T3tkNdV6phLTwEj6Hejp5FR13ZB6jDScUCpTV0yQ@mail.gmail.com> (raw)
In-Reply-To: <CANn89iJm3Pokx2hJy4af-frhV2+cadRYBSydG2Pc5w3C7d8RrA@mail.gmail.com>
On Wed, Apr 17, 2024 at 7:58 PM Eric Dumazet <edumazet@google.com> wrote:
>
> On Wed, Apr 17, 2024 at 1:52 PM Eric Dumazet <edumazet@google.com> wrote:
> >
> > @@ -4668,7 +4668,7 @@ bool rps_may_expire_flow(struct net_device *dev,
> > u16 rxq_index,
> > cpu = READ_ONCE(rflow->cpu);
> > if (rflow->filter == filter_id && cpu < nr_cpu_ids &&
> > ((int)(READ_ONCE(per_cpu(softnet_data,
> > cpu).input_queue_head) -
> > - READ_ONCE(rflow->last_qtail)) <
> > + rflow->last_qtail) <
> > (int)(10 * flow_table->mask)))
> > expire = false;
> > }
>
> Oh well, rps_may_expire_flow() might be called from other contexts, so
> only the READ_ONCE()
> from get_rps_cpu() is not really necessary.
Thanks for telling me the access logic about qtail in the previous email.
Yes, I'm writing exactly what you're saying now :) I can keep
protecting rflow->cpu and rflow->filter locklessly.
I can remove the unneeded annotations around qtail as you suggested
with those two patches if I can, or you can submit it first. It's up
to you :)
Thanks,
Jason
next prev parent reply other threads:[~2024-04-17 12:14 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
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 [this message]
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=CAL+tcoCW2-T3tkNdV6phLTwEj6Hejp5FR13ZB6jDScUCpTV0yQ@mail.gmail.com \
--to=kerneljasonxing@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--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).