[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250801161440.6f8aeee8@kernel.org>
Date: Fri, 1 Aug 2025 16:14:40 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Mina Almasry <almasrymina@...gle.com>
Cc: Pavel Begunkov <asml.silence@...il.com>, netdev@...r.kernel.org,
io-uring@...r.kernel.org, Eric Dumazet <edumazet@...gle.com>, Willem de
Bruijn <willemb@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
andrew+netdev@...n.ch, horms@...nel.org, davem@...emloft.net,
sdf@...ichev.me, dw@...idwei.uk, michael.chan@...adcom.com,
dtatulea@...dia.com, ap420073@...il.com
Subject: Re: [RFC v1 04/22] net: clarify the meaning of netdev_config
members
On Mon, 28 Jul 2025 14:44:19 -0700 Mina Almasry wrote:
> > struct netdev_config {
> > + /* Direct value
> > + *
> > + * Driver default is expected to be fixed, and set in this struct
> > + * at init. From that point on user may change the value. There is
> > + * no explicit way to "unset" / restore driver default.
> > + */
>
> Does the user setting hds_thres imply turning hds_config to "on"? Or
> is hds_thres only used when hds_config is actually on?
The latter.
Powered by blists - more mailing lists