[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250425164136.03b38e7c@kernel.org>
Date: Fri, 25 Apr 2025 16:41:36 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Stanislav Fomichev <stfomichev@...il.com>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
pabeni@...hat.com, andrew+netdev@...n.ch, horms@...nel.org,
donald.hunter@...il.com, sdf@...ichev.me, almasrymina@...gle.com,
dw@...idwei.uk, asml.silence@...il.com, ap420073@...il.com,
jdamato@...tly.com, dtatulea@...dia.com, michael.chan@...adcom.com
Subject: Re: [RFC net-next 17/22] netdev: add support for setting rx-buf-len
per queue
On Tue, 22 Apr 2025 09:15:59 -0700 Stanislav Fomichev wrote:
> > + -
> > + name: queue-set
> > + doc: Set per-queue configurable options.
> > + attribute-set: queue
> > + do:
> > + request:
> > + attributes:
> > + - ifindex
> > + - type
> > + - id
> > + - rx-buf-len
>
> Do we want some guidance going forward on what belongs to queue-set
> vs napi-set? (mostly) HW settings for the queue-set and (mostly) SW
> settings for (serving the queues) in napi-set?
One NAPI can have multiple queues hanging off, so all HW settings
with the exception of IRQ coalescing should probably be on the queue?
Powered by blists - more mailing lists