All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: "Chia-Yu Chang (Nokia)" <chia-yu.chang@nokia-bell-labs.com>
Cc: "alok.a.tiwari@oracle.com" <alok.a.tiwari@oracle.com>,
	"pctammela@mojatatu.com" <pctammela@mojatatu.com>,
	"horms@kernel.org" <horms@kernel.org>,
	"donald.hunter@gmail.com" <donald.hunter@gmail.com>,
	"xandfury@gmail.com" <xandfury@gmail.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"dave.taht@gmail.com" <dave.taht@gmail.com>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"jhs@mojatatu.com" <jhs@mojatatu.com>,
	"stephen@networkplumber.org" <stephen@networkplumber.org>,
	"xiyou.wangcong@gmail.com" <xiyou.wangcong@gmail.com>,
	"jiri@resnulli.us" <jiri@resnulli.us>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"edumazet@google.com" <edumazet@google.com>,
	"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
	"ast@fiberby.net" <ast@fiberby.net>,
	"liuhangbin@gmail.com" <liuhangbin@gmail.com>,
	"shuah@kernel.org" <shuah@kernel.org>,
	"linux-kselftest@vger.kernel.org"
	<linux-kselftest@vger.kernel.org>,
	"ij@kernel.org" <ij@kernel.org>,
	"ncardwell@google.com" <ncardwell@google.com>,
	"Koen De Schepper (Nokia)" <koen.de_schepper@nokia-bell-labs.com>,
	"g.white@cablelabs.com" <g.white@cablelabs.com>,
	"ingemar.s.johansson@ericsson.com"
	<ingemar.s.johansson@ericsson.com>,
	"mirja.kuehlewind@ericsson.com" <mirja.kuehlewind@ericsson.com>,
	"cheshire@apple.com" <cheshire@apple.com>,
	"rs.ietf@gmx.at" <rs.ietf@gmx.at>,
	"Jason_Livingood@comcast.com" <Jason_Livingood@comcast.com>,
	"vidhi_goel@apple.com" <vidhi_goel@apple.com>
Subject: Re: [PATCH v20 net-next 1/6] sched: Struct definition and parsing of dualpi2 qdisc
Date: Mon, 30 Jun 2025 08:13:49 -0700	[thread overview]
Message-ID: <20250630081349.4c9d7976@kernel.org> (raw)
In-Reply-To: <PAXPR07MB79849FDC079A2ECB144D75D1A347A@PAXPR07MB7984.eurprd07.prod.outlook.com>

On Sun, 29 Jun 2025 22:49:24 +0000 Chia-Yu Chang (Nokia) wrote:
> > I don't get the reason for all these WRITE_ONCE()s.
> > You lock the qdisc to make modifications, right?
> > And the block under which I'm responding is performing two dependent writes, one to ->step_in_packets and the other to ->step_thresh a change which is definitely not atomic..  
> 
> Thanks again for other comments again, and I will take actions in the next version.
> 
> As there is only one step marking in L-queue, so we still need two
> WRITE_ONCE even two attributes (one for threshold in packets and one
> in time) are used.
> 
> When applying the step marking, we need to know either the
> computation is based on the sojourn time or queue length.

Let me ask again - why do you use WRITE_ONCE() at all if 
the modification takes the qdisc lock? Which reader are
you afraid of racing with?

  reply	other threads:[~2025-06-30 15:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-21 19:33 [PATCH v20 net-next 0/6] DUALPI2 patch chia-yu.chang
2025-06-21 19:33 ` [PATCH v20 net-next 1/6] sched: Struct definition and parsing of dualpi2 qdisc chia-yu.chang
2025-06-24 11:01   ` Paolo Abeni
2025-06-27 23:25   ` Jakub Kicinski
2025-06-29 22:49     ` Chia-Yu Chang (Nokia)
2025-06-30 15:13       ` Jakub Kicinski [this message]
2025-06-30 15:51         ` Chia-Yu Chang (Nokia)
2025-06-30 16:23           ` Jakub Kicinski
2025-06-30 17:04             ` Chia-Yu Chang (Nokia)
2025-06-30 23:43               ` Jakub Kicinski
2025-07-01  5:41                 ` Chia-Yu Chang (Nokia)
2025-07-01 23:30                   ` Jakub Kicinski
2025-06-21 19:33 ` [PATCH v20 net-next 2/6] sched: Dump configuration and statistics " chia-yu.chang
2025-06-21 19:33 ` [PATCH v20 net-next 3/6] sched: Add enqueue/dequeue " chia-yu.chang
2025-06-21 19:33 ` [PATCH v20 net-next 4/6] selftests/tc-testing: Fix warning and style check on tdc.sh chia-yu.chang
2025-06-21 19:33 ` [PATCH v20 net-next 5/6] selftests/tc-testing: Add selftests for qdisc DualPI2 chia-yu.chang
2025-06-21 19:33 ` [PATCH v20 net-next 6/6] Documentation: netlink: specs: tc: Add DualPI2 specification chia-yu.chang
2025-06-27 23:19   ` Jakub Kicinski
2025-06-29 22:32     ` Chia-Yu Chang (Nokia)
2025-06-30 15:12       ` Jakub Kicinski
2025-06-30 15:27         ` Chia-Yu Chang (Nokia)
2025-06-30 16:23           ` Jakub Kicinski
2025-06-24 11:08 ` [PATCH v20 net-next 0/6] DUALPI2 patch Paolo Abeni
2025-06-24 12:34 ` Ferenc Fejes
2025-06-24 13:53   ` Koen De Schepper (Nokia)
2025-06-25 10:10     ` Simon Horman

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=20250630081349.4c9d7976@kernel.org \
    --to=kuba@kernel.org \
    --cc=Jason_Livingood@comcast.com \
    --cc=alok.a.tiwari@oracle.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=ast@fiberby.net \
    --cc=cheshire@apple.com \
    --cc=chia-yu.chang@nokia-bell-labs.com \
    --cc=dave.taht@gmail.com \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=g.white@cablelabs.com \
    --cc=horms@kernel.org \
    --cc=ij@kernel.org \
    --cc=ingemar.s.johansson@ericsson.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=koen.de_schepper@nokia-bell-labs.com \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=liuhangbin@gmail.com \
    --cc=mirja.kuehlewind@ericsson.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pctammela@mojatatu.com \
    --cc=rs.ietf@gmx.at \
    --cc=shuah@kernel.org \
    --cc=stephen@networkplumber.org \
    --cc=vidhi_goel@apple.com \
    --cc=xandfury@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.