[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241009201440.418e21de@kernel.org>
Date: Wed, 9 Oct 2024 20:14:40 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Joe Damato <jdamato@...tly.com>
Cc: netdev@...r.kernel.org, mkarsten@...terloo.ca, skhawaja@...gle.com,
sdf@...ichev.me, bjorn@...osinc.com, amritha.nambiar@...el.com,
sridhar.samudrala@...el.com, willemdebruijn.kernel@...il.com, "David S.
Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo
Abeni <pabeni@...hat.com>, Donald Hunter <donald.hunter@...il.com>, Jesper
Dangaard Brouer <hawk@...nel.org>, Mina Almasry <almasrymina@...gle.com>,
Xuan Zhuo <xuanzhuo@...ux.alibaba.com>, linux-kernel@...r.kernel.org (open
list)
Subject: Re: [net-next v5 4/9] netdev-genl: Dump gro_flush_timeout
On Wed, 9 Oct 2024 00:54:58 +0000 Joe Damato wrote:
> + name: gro-flush-timeout
> + doc: The timeout, in nanoseconds, of when to trigger the NAPI
> + watchdog timer and schedule NAPI processing.
You gotta respin because we reformatted the cacheline info.
So while at it perhaps throw in a sentence here about the GRO effects?
The initial use of GRO flush timeout was to hold incomplete GRO
super-frames in the GRO engine across NAPI cycles.
Powered by blists - more mailing lists