From: Jakub Kicinski <kuba@kernel.org>
To: Joe Damato <jdamato@fastly.com>
Cc: netdev@vger.kernel.org, mkarsten@uwaterloo.ca,
skhawaja@google.com, sdf@fomichev.me, bjorn@rivosinc.com,
amritha.nambiar@intel.com, sridhar.samudrala@intel.com,
willemdebruijn.kernel@gmail.com,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Donald Hunter <donald.hunter@gmail.com>,
Jesper Dangaard Brouer <hawk@kernel.org>,
Mina Almasry <almasrymina@google.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
linux-kernel@vger.kernel.org (open list)
Subject: Re: [net-next v5 4/9] netdev-genl: Dump gro_flush_timeout
Date: Wed, 9 Oct 2024 20:14:40 -0700 [thread overview]
Message-ID: <20241009201440.418e21de@kernel.org> (raw)
In-Reply-To: <20241009005525.13651-5-jdamato@fastly.com>
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.
next prev parent reply other threads:[~2024-10-10 3:14 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 0:54 [net-next v5 0/9] Add support for per-NAPI config via netlink Joe Damato
2024-10-09 0:54 ` [net-next v5 1/9] net: napi: Make napi_defer_hard_irqs per-NAPI Joe Damato
2024-10-10 4:10 ` Eric Dumazet
2024-10-09 0:54 ` [net-next v5 2/9] netdev-genl: Dump napi_defer_hard_irqs Joe Damato
2024-10-10 4:11 ` Eric Dumazet
2024-10-09 0:54 ` [net-next v5 3/9] net: napi: Make gro_flush_timeout per-NAPI Joe Damato
2024-10-10 4:13 ` Eric Dumazet
2024-10-09 0:54 ` [net-next v5 4/9] netdev-genl: Dump gro_flush_timeout Joe Damato
2024-10-10 3:14 ` Jakub Kicinski [this message]
2024-10-10 4:34 ` Joe Damato
2024-10-10 4:45 ` Eric Dumazet
2024-10-10 4:59 ` Joe Damato
2024-10-09 0:54 ` [net-next v5 5/9] net: napi: Add napi_config Joe Damato
2024-10-10 4:20 ` Eric Dumazet
2024-10-10 15:59 ` Joe Damato
2024-10-10 16:08 ` Jakub Kicinski
2024-10-09 0:55 ` [net-next v5 6/9] netdev-genl: Support setting per-NAPI config values Joe Damato
2024-10-10 4:24 ` Eric Dumazet
2024-10-10 15:19 ` Jakub Kicinski
2024-10-10 15:30 ` Eric Dumazet
2024-10-10 16:40 ` Joe Damato
2024-10-11 17:19 ` Eric Dumazet
2024-10-11 17:50 ` Joe Damato
2024-10-09 0:55 ` [net-next v5 7/9] bnxt: Add support for persistent NAPI config Joe Damato
2024-10-10 4:25 ` Eric Dumazet
2024-10-09 0:55 ` [net-next v5 8/9] mlx5: " Joe Damato
2024-10-10 4:26 ` Eric Dumazet
2024-10-09 0:55 ` [net-next v5 9/9] mlx4: Add support for persistent NAPI config to RX CQs Joe Damato
2024-10-10 4:28 ` Eric Dumazet
2024-10-10 16:07 ` Joe Damato
2024-10-10 3:17 ` [net-next v5 0/9] Add support for per-NAPI config via netlink Jakub Kicinski
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=20241009201440.418e21de@kernel.org \
--to=kuba@kernel.org \
--cc=almasrymina@google.com \
--cc=amritha.nambiar@intel.com \
--cc=bjorn@rivosinc.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=jdamato@fastly.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mkarsten@uwaterloo.ca \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=skhawaja@google.com \
--cc=sridhar.samudrala@intel.com \
--cc=willemdebruijn.kernel@gmail.com \
--cc=xuanzhuo@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).