netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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,
	"Toke Høiland-Jørgensen" <toke@toke.dk>,
	cake@lists.bufferbloat.net
Subject: Re: [PATCH net-next 02/14] net_sched: cake: implement lockless cake_dump()
Date: Wed, 17 Apr 2024 10:24:57 +0100	[thread overview]
Message-ID: <20240417092457.GV2320920@kernel.org> (raw)
In-Reply-To: <CANn89i+MF3F8Q063USmLYvyrffBKQRvb3ZM2c1MhAbFOwk9B-A@mail.gmail.com>

On Wed, Apr 17, 2024 at 10:54:30AM +0200, Eric Dumazet wrote:
> On Wed, Apr 17, 2024 at 10:35 AM Simon Horman <horms@kernel.org> wrote:
> >
> > + Toke Høiland-Jørgensen <toke@toke.dk>
> >   cake@lists.bufferbloat.net
> >
> > On Mon, Apr 15, 2024 at 01:20:42PM +0000, Eric Dumazet wrote:
> > > Instead of relying on RTNL, cake_dump() can use READ_ONCE()
> > > annotations, paired with WRITE_ONCE() ones in cake_change().
> > >
> > > Signed-off-by: Eric Dumazet <edumazet@google.com>
> >
> > ...
> >
> > > @@ -2774,68 +2783,71 @@ static int cake_dump(struct Qdisc *sch, struct sk_buff *skb)
> > >  {
> > >       struct cake_sched_data *q = qdisc_priv(sch);
> > >       struct nlattr *opts;
> > > +     u16 rate_flags;
> > >
> > >       opts = nla_nest_start_noflag(skb, TCA_OPTIONS);
> > >       if (!opts)
> > >               goto nla_put_failure;
> > >
> > > -     if (nla_put_u64_64bit(skb, TCA_CAKE_BASE_RATE64, q->rate_bps,
> > > -                           TCA_CAKE_PAD))
> > > +     if (nla_put_u64_64bit(skb, TCA_CAKE_BASE_RATE64,
> > > +                           READ_ONCE(q->rate_bps), TCA_CAKE_PAD))
> > >               goto nla_put_failure;
> > >
> > >       if (nla_put_u32(skb, TCA_CAKE_FLOW_MODE,
> > > -                     q->flow_mode & CAKE_FLOW_MASK))
> > > +                     READ_ONCE(q->flow_mode) & CAKE_FLOW_MASK))
> > >               goto nla_put_failure;
> >
> > Hi Eric,
> >
> > q->flow_mode is read twice in this function. Once here...
> >
> > >
> > > -     if (nla_put_u32(skb, TCA_CAKE_RTT, q->interval))
> > > +     if (nla_put_u32(skb, TCA_CAKE_RTT, READ_ONCE(q->interval)))
> > >               goto nla_put_failure;
> > >
> > > -     if (nla_put_u32(skb, TCA_CAKE_TARGET, q->target))
> > > +     if (nla_put_u32(skb, TCA_CAKE_TARGET, READ_ONCE(q->target)))
> > >               goto nla_put_failure;
> > >
> > > -     if (nla_put_u32(skb, TCA_CAKE_MEMORY, q->buffer_config_limit))
> > > +     if (nla_put_u32(skb, TCA_CAKE_MEMORY,
> > > +                     READ_ONCE(q->buffer_config_limit)))
> > >               goto nla_put_failure;
> > >
> > > +     rate_flags = READ_ONCE(q->rate_flags);
> > >       if (nla_put_u32(skb, TCA_CAKE_AUTORATE,
> > > -                     !!(q->rate_flags & CAKE_FLAG_AUTORATE_INGRESS)))
> > > +                     !!(rate_flags & CAKE_FLAG_AUTORATE_INGRESS)))
> > >               goto nla_put_failure;
> > >
> > >       if (nla_put_u32(skb, TCA_CAKE_INGRESS,
> > > -                     !!(q->rate_flags & CAKE_FLAG_INGRESS)))
> > > +                     !!(rate_flags & CAKE_FLAG_INGRESS)))
> > >               goto nla_put_failure;
> > >
> > > -     if (nla_put_u32(skb, TCA_CAKE_ACK_FILTER, q->ack_filter))
> > > +     if (nla_put_u32(skb, TCA_CAKE_ACK_FILTER, READ_ONCE(q->ack_filter)))
> > >               goto nla_put_failure;
> > >
> > >       if (nla_put_u32(skb, TCA_CAKE_NAT,
> > > -                     !!(q->flow_mode & CAKE_FLOW_NAT_FLAG)))
> > > +                     !!(READ_ONCE(q->flow_mode) & CAKE_FLOW_NAT_FLAG)))
> > >               goto nla_put_failure;
> >
> > ... and once here.
> >
> > I am assuming that it isn't a big deal, but perhaps it is better to save
> > q->flow_mode into a local variable.
> >
> > Also, more importantly, q->flow_mode does not seem to be handled
> > using WRITE_ONCE() in cake_change(). It's a non-trivial case,
> > which I guess is well served by a mechanism built around a local variable.
> 
> Thanks !
> 
> I will squash in v2:

Likewise, thanks.
This looks good to me.

...

  reply	other threads:[~2024-04-17  9:25 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 [this message]
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
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=20240417092457.GV2320920@kernel.org \
    --to=horms@kernel.org \
    --cc=cake@lists.bufferbloat.net \
    --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=toke@toke.dk \
    --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).