Netdev List
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Larysa Zaremba <larysa.zaremba@intel.com>,
	Jakub Raczynski <j.raczynski@samsung.com>
Cc: <netdev@vger.kernel.org>, <andrew+netdev@lunn.ch>,
	<davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
	<mcoquelin.stm32@gmail.com>, <alexandre.torgue@foss.st.com>,
	<linux-kernel@vger.kernel.org>, <k.domagalski@samsung.com>,
	<k.tegowski@samsung.com>, <cs0617.lee@samsung.com>
Subject: Re: [PATCH net-next v2 1/3] net/stmmac/dwxgmac: Modify DMA functions for future hardware
Date: Fri, 5 Jun 2026 19:02:10 -0700	[thread overview]
Message-ID: <20260605190210.13d9b18c@kernel.org> (raw)
In-Reply-To: <aiAiAbasQA3B3aT_@soc-5CG4396X81.clients.intel.com>

On Wed, 3 Jun 2026 14:45:53 +0200 Larysa Zaremba wrote:
> > > Because dwxgmac2_set_mtl_tx_queue_weight() returns void and is invoked via
> > > the stmmac_do_void_callback() macro (which unconditionally returns 0), will
> > > this early return cause ETS qdisc queue weighting on higher queue indices
> > > to silently fail? 
> > > It appears userspace will receive a success code while the hardware is left
> > > unconfigured.
> > 
> > As talked in previous mailing, answer is yes, there will be error in dmesg,
> > but no fail, for very simple reason that we would need to rewrite A LOT to add
> > proper error handling.
> > I just hope that if user misconfigured this stuff they will read this error
> > and fix it rather than complain.
> 
> But previously those callbacks did not have any failure conditions, so I would 
> say that adding a message-only failure does constitute a minor regression.

+1, this feels a bit sloppy. The driver has some painful abstraction
layers but if we cut ourselves some slack because of that that'd be
basically encouraging shitty architectures.
-- 
pw-bot: cr

  reply	other threads:[~2026-06-06  2:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20260601162617eucas1p2efc386a4d9f9e7e98e8acb83f9c550d6@eucas1p2.samsung.com>
2026-06-01 16:25 ` [PATCH net-next v2 0/3] xgmac: Support for 16 MTL/DMA queues Jakub Raczynski
2026-06-01 16:25   ` [PATCH net-next v2 1/3] net/stmmac/dwxgmac: Modify DMA functions for future hardware Jakub Raczynski
2026-06-03 11:46     ` Jakub Raczynski
2026-06-03 12:45       ` Larysa Zaremba
2026-06-06  2:02         ` Jakub Kicinski [this message]
2026-06-01 16:25   ` [PATCH net-next v2 2/3] net/stmmac/dwxgmac: Extend MTL/DMA support to 16 queues Jakub Raczynski
2026-06-03 14:23     ` Larysa Zaremba
2026-06-01 16:25   ` [PATCH net-next v2 3/3] include/stmmac: Increase max DMA/MTL channel count from 8 to 16 Jakub Raczynski
2026-06-04 13:16     ` Paolo Abeni

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=20260605190210.13d9b18c@kernel.org \
    --to=kuba@kernel.org \
    --cc=alexandre.torgue@foss.st.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=cs0617.lee@samsung.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=j.raczynski@samsung.com \
    --cc=k.domagalski@samsung.com \
    --cc=k.tegowski@samsung.com \
    --cc=larysa.zaremba@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcoquelin.stm32@gmail.com \
    --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