Netdev List
 help / color / mirror / Atom feed
From: Justin Chen <justin.chen@broadcom.com>
To: Nicolai Buchwitz <nb@tipi-net.de>
Cc: Ovidiu Panait <ovidiu.panait.rb@renesas.com>,
	opendmb@gmail.com, florian.fainelli@broadcom.com,
	bcm-kernel-feedback-list@broadcom.com, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: bcmgenet: Use weighted round-robin TX DMA arbitration
Date: Fri, 12 Jun 2026 10:34:34 -0700	[thread overview]
Message-ID: <0ada80c4-0ad0-4475-9a5c-173ead88a4dc@broadcom.com> (raw)
In-Reply-To: <69d920a3b52cc049dc1b96a9c7d5e3b6@tipi-net.de>



On 6/12/26 12:37 AM, Nicolai Buchwitz wrote:
> On 11.6.2026 19:27, Justin Chen wrote:
> 
>> [...]
> 
>>> AFAIK the existing queue mechanism dates back to the STB QoS use 
>>> cases Florian
>>> had in mind when he wrote the driver, so let's hear what he has to 
>>> say on this.
>>>
>>> The change itself looks correct to me. My concern is the targeting. This
>>> flips the default policy for every GENET user rather than fixing a 
>>> specific
>>> defect, and Justin's series already called the persistent timeouts a 
>>> design
>>> issue rather than a bug.
>>>
>>> So isn't this more net-next material than net with a broad Fixes: tag?
>>> Please also add to the commit message that it drops the existing 
>>> priority
>>> handling for rings 1-4.
>>>
>>
>> I'm ok with these changes. Internally we no longer require priority 
>> queues. It is a legacy use case we no longer have. My idea was to 
>> remove the queues entirely and have one big queue. But I figured I 
>> would wait for Nicolai's XDP changes so we do not need to remove and 
>> re-add queues for XDP. This could be a stop-gap solution until that is 
>> done.
> 
> Thanks Justin. IMHO XDP could benefit from a queue-refactoring prep. It 
> gets simpler on top of a single queue, and dropping q1-4 frees up a 
> bunch of BDs for the XDP ring instead of the 32 it has atm.
> 
> Happy to take it on, or leave it to you :)
> 

I am not going to say no to less work! Please do.

Thanks,
Justin

>> [...]
> 
> Thanks
> Nicolai


  reply	other threads:[~2026-06-12 17:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10  8:52 [PATCH net] net: bcmgenet: Use weighted round-robin TX DMA arbitration Ovidiu Panait
2026-06-11  8:08 ` Nicolai Buchwitz
2026-06-11 17:27   ` Justin Chen
2026-06-12  7:37     ` Nicolai Buchwitz
2026-06-12 17:34       ` Justin Chen [this message]
2026-06-13 22:00 ` patchwork-bot+netdevbpf

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=0ada80c4-0ad0-4475-9a5c-173ead88a4dc@broadcom.com \
    --to=justin.chen@broadcom.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nb@tipi-net.de \
    --cc=netdev@vger.kernel.org \
    --cc=opendmb@gmail.com \
    --cc=ovidiu.panait.rb@renesas.com \
    --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