From: Simon Horman <horms@kernel.org>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>,
netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 05/14] net_sched: sch_codel: implement lockless codel_dump()
Date: Wed, 17 Apr 2024 16:59:09 +0100 [thread overview]
Message-ID: <20240417155909.GZ2320920@kernel.org> (raw)
In-Reply-To: <20240415132054.3822230-6-edumazet@google.com>
On Mon, Apr 15, 2024 at 01:20:45PM +0000, Eric Dumazet wrote:
> Instead of relying on RTNL, codel_dump() can use READ_ONCE()
> annotations, paired with WRITE_ONCE() ones in codel_change().
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> ---
> net/sched/sch_codel.c | 29 ++++++++++++++++++-----------
> 1 file changed, 18 insertions(+), 11 deletions(-)
>
> diff --git a/net/sched/sch_codel.c b/net/sched/sch_codel.c
> index ecb3f164bb25b33bd662c8ee07dc1b5945fd882d..3e8d4fe4d91e3ef2b7715640f6675aa5e8e2a326 100644
> --- a/net/sched/sch_codel.c
> +++ b/net/sched/sch_codel.c
> @@ -118,26 +118,31 @@ static int codel_change(struct Qdisc *sch, struct nlattr *opt,
> if (tb[TCA_CODEL_TARGET]) {
> u32 target = nla_get_u32(tb[TCA_CODEL_TARGET]);
>
> - q->params.target = ((u64)target * NSEC_PER_USEC) >> CODEL_SHIFT;
> + WRITE_ONCE(q->params.target,
> + ((u64)target * NSEC_PER_USEC) >> CODEL_SHIFT);
> }
>
> if (tb[TCA_CODEL_CE_THRESHOLD]) {
> u64 val = nla_get_u32(tb[TCA_CODEL_CE_THRESHOLD]);
>
> - q->params.ce_threshold = (val * NSEC_PER_USEC) >> CODEL_SHIFT;
> + WRITE_ONCE(q->params.ce_threshold,
> + (val * NSEC_PER_USEC) >> CODEL_SHIFT);
> }
>
> if (tb[TCA_CODEL_INTERVAL]) {
> u32 interval = nla_get_u32(tb[TCA_CODEL_INTERVAL]);
>
> - q->params.interval = ((u64)interval * NSEC_PER_USEC) >> CODEL_SHIFT;
> + WRITE_ONCE(q->params.interval,
> + ((u64)interval * NSEC_PER_USEC) >> CODEL_SHIFT);
> }
>
> if (tb[TCA_CODEL_LIMIT])
> - sch->limit = nla_get_u32(tb[TCA_CODEL_LIMIT]);
> + WRITE_ONCE(sch->limit,
> + nla_get_u32(tb[TCA_CODEL_LIMIT]));
>
Hi Eric,
Sorry to be so bothersome.
As a follow-up to our discussion of patch 4/14 (net_choke),
I'm wondering if reading sch->limit in codel_qdisc_enqueue()
should be updated to use READ_ONCE().
> if (tb[TCA_CODEL_ECN])
> - q->params.ecn = !!nla_get_u32(tb[TCA_CODEL_ECN]);
> + WRITE_ONCE(q->params.ecn,
> + !!nla_get_u32(tb[TCA_CODEL_ECN]));
>
> qlen = sch->q.qlen;
> while (sch->q.qlen > sch->limit) {
...
next prev parent reply other threads:[~2024-04-17 15:59 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 13:20 [PATCH net-next 00/14] net_sched: first series for RTNL-less qdisc dumps Eric Dumazet
2024-04-15 13:20 ` [PATCH net-next 01/14] net_sched: sch_fq: implement lockless fq_dump() Eric Dumazet
2024-04-16 18:19 ` Simon Horman
2024-04-16 18:33 ` Eric Dumazet
2024-04-17 8:45 ` Eric Dumazet
2024-04-17 9:00 ` Simon Horman
2024-04-17 9:02 ` Eric Dumazet
2024-04-17 9:23 ` Simon Horman
2024-04-15 13:20 ` [PATCH net-next 02/14] net_sched: cake: implement lockless cake_dump() Eric Dumazet
2024-04-17 8:35 ` Simon Horman
2024-04-17 8:54 ` Eric Dumazet
2024-04-17 9:24 ` Simon Horman
2024-04-17 12:25 ` Toke Høiland-Jørgensen
2024-04-15 13:20 ` [PATCH net-next 03/14] net_sched: sch_cbs: implement lockless cbs_dump() Eric Dumazet
2024-04-17 9:27 ` Simon Horman
2024-04-15 13:20 ` [PATCH net-next 04/14] net_sched: sch_choke: implement lockless choke_dump() Eric Dumazet
2024-04-17 13:14 ` Simon Horman
2024-04-17 13:41 ` Eric Dumazet
2024-04-17 14:44 ` Simon Horman
2024-04-15 13:20 ` [PATCH net-next 05/14] net_sched: sch_codel: implement lockless codel_dump() Eric Dumazet
2024-04-17 15:59 ` Simon Horman [this message]
2024-04-17 16:05 ` Eric Dumazet
2024-04-17 16:21 ` Simon Horman
2024-04-15 13:20 ` [PATCH net-next 06/14] net_sched: sch_tfs: implement lockless etf_dump() Eric Dumazet
2024-04-17 16:27 ` Simon Horman
2024-04-15 13:20 ` [PATCH net-next 07/14] net_sched: sch_ets: implement lockless ets_dump() Eric Dumazet
2024-04-17 16:54 ` Simon Horman
2024-04-17 17:08 ` Eric Dumazet
2024-04-17 17:17 ` Simon Horman
2024-04-15 13:20 ` [PATCH net-next 08/14] net_sched: sch_fifo: implement lockless __fifo_dump() Eric Dumazet
2024-04-15 13:20 ` [PATCH net-next 09/14] net_sched: sch_fq_codel: implement lockless fq_codel_dump() Eric Dumazet
2024-04-17 17:07 ` Simon Horman
2024-04-17 17:14 ` Eric Dumazet
2024-04-17 17:22 ` Simon Horman
2024-04-15 13:20 ` [PATCH net-next 10/14] net_sched: sch_fq_pie: implement lockless fq_pie_dump() Eric Dumazet
2024-04-17 17:13 ` Simon Horman
2024-04-17 17:15 ` Eric Dumazet
2024-04-17 17:23 ` Simon Horman
2024-04-15 13:20 ` [PATCH net-next 11/14] net_sched: sch_hfsc: implement lockless accesses to q->defcls Eric Dumazet
2024-04-15 13:20 ` [PATCH net-next 12/14] net_sched: sch_hhf: implement lockless hhf_dump() Eric Dumazet
2024-04-17 17:26 ` Simon Horman
2024-04-15 13:20 ` [PATCH net-next 13/14] net_sched: sch_pie: implement lockless pie_dump() Eric Dumazet
2024-04-17 17:28 ` Simon Horman
2024-04-15 13:20 ` [PATCH net-next 14/14] net_sched: sch_skbprio: implement lockless skbprio_dump() Eric Dumazet
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=20240417155909.GZ2320920@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=xiyou.wangcong@gmail.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).