netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Xing <kerneljasonxing@gmail.com>
To: edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	 davem@davemloft.net, horms@kernel.org
Cc: netdev@vger.kernel.org, Jason Xing <kernelxing@tencent.com>
Subject: Re: [PATCH net-next 1/3] net: rps: protect last_qtail with rps_input_queue_tail_save() helper
Date: Wed, 17 Apr 2024 08:26:18 +0800	[thread overview]
Message-ID: <CAL+tcoD19X_ijKsLQu3cWaLsk8saeEAqQ8MWiJstDMJuWvbNfQ@mail.gmail.com> (raw)
In-Reply-To: <20240416074232.23525-2-kerneljasonxing@gmail.com>

On Tue, Apr 16, 2024 at 3:42 PM Jason Xing <kerneljasonxing@gmail.com> wrote:
>
> From: Jason Xing <kernelxing@tencent.com>
>
> Only one left place should be proctected locklessly. This patch made it.
>
> Signed-off-by: Jason Xing <kernelxing@tencent.com>
> ---
>  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 854a3a28a8d8..cd97eeae8218 100644
> --- a/net/core/dev.c
> +++ b/net/core/dev.c
> @@ -4501,7 +4501,7 @@ set_rps_cpu(struct net_device *dev, struct sk_buff *skb,
>                 struct netdev_rx_queue *rxqueue;
>                 struct rps_dev_flow_table *flow_table;
>                 struct rps_dev_flow *old_rflow;
> -               u32 flow_id;
> +               u32 flow_id, head;
>                 u16 rxq_index;
>                 int rc;
>
> @@ -4529,8 +4529,8 @@ set_rps_cpu(struct net_device *dev, struct sk_buff *skb,
>                         old_rflow->filter = RPS_NO_FILTER;
>         out:
>  #endif
> -               rflow->last_qtail =
> -                       READ_ONCE(per_cpu(softnet_data, next_cpu).input_queue_head);
> +               head = READ_ONCE(per_cpu(softnet_data, next_cpu).input_queue_head);
> +               rps_input_queue_tail_save(rflow->last_qtail, head);

I made a mistake. I should pass &rflow->last_qtail actually. Will update it.

>         }
>
>         rflow->cpu = next_cpu;
> --
> 2.37.3
>

  reply	other threads:[~2024-04-17  0:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16  7:42 [PATCH net-next 0/3] locklessly protect left members in struct rps_dev_flow Jason Xing
2024-04-16  7:42 ` [PATCH net-next 1/3] net: rps: protect last_qtail with rps_input_queue_tail_save() helper Jason Xing
2024-04-17  0:26   ` Jason Xing [this message]
2024-04-16  7:42 ` [PATCH net-next 2/3] net: rps: protect filter locklessly Jason Xing
2024-04-16  7:42 ` [PATCH net-next 3/3] net: rps: locklessly access rflow->cpu 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+tcoD19X_ijKsLQu3cWaLsk8saeEAqQ8MWiJstDMJuWvbNfQ@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).