[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240306201913.626a41f0@kernel.org>
Date: Wed, 6 Mar 2024 20:19:13 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Pavan Chebbi <pavan.chebbi@...adcom.com>
Cc: Vadim Fedorenko <vadim.fedorenko@...ux.dev>, Jiri Pirko
<jiri@...nulli.us>, Michael Chan <michael.chan@...adcom.com>,
davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
pabeni@...hat.com, andrew.gospodarek@...adcom.com, richardcochran@...il.com
Subject: Re: [PATCH net-next 1/2] bnxt_en: Introduce devlink runtime driver
param to set ptp tx timeout
On Thu, 7 Mar 2024 09:20:44 +0530 Pavan Chebbi wrote:
> > > As such timeouts are rare but still normal.
> >
> > Normal, because...? Why do they happen?
>
> Excuse me for the late reply.
> In my experience so far, it's primarily because of flow control and
> how stressed the underlying HW queue is. (I am sure it's not unique to
> our hardware alone)
> Hence we wanted to accommodate cases where the expected wait time is
> higher than what is default in the driver, for the packets to go out.
> But it's disappointing to know that even private devlink params are
> discouraged for such purposes.
> I'd think that non-generic driver params in devlink serve exactly such
> requirements and having such a knob would be useful for an advanced
> user.
> Not to mention, in my view, such additions to devlink would make it
> more popular and would help in its wider adoption.
The problem can be solved more intelligently.
Powered by blists - more mailing lists