From: Gabriel Goller <g.goller@proxmox.com>
To: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>
Cc: netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH net-next v2] docs: net: document neigh gc_stale_time sysctl
Date: Mon, 23 Feb 2026 11:12:54 +0100 [thread overview]
Message-ID: <20260223101257.47563-1-g.goller@proxmox.com> (raw)
Add missing documentation for a neighbor table garbage collector sysctl
parameter in ip-sysctl.rst:
neigh/default/gc_stale_time: controls how long an unused neighbor entry
is kept before becoming eligible for garbage collection (default: 60
seconds)
Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
---
Changelog:
v1:
* removed documentation for gc_interval, as that sysctl is not used
anymore and doesn't do anything.
* mention gc_stale_time only being used when we have more than
gc_thresh1 neighbors.
Documentation/networking/ip-sysctl.rst | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/Documentation/networking/ip-sysctl.rst b/Documentation/networking/ip-sysctl.rst
index 28c7e4f5ecf9..85fda3759534 100644
--- a/Documentation/networking/ip-sysctl.rst
+++ b/Documentation/networking/ip-sysctl.rst
@@ -202,6 +202,17 @@ neigh/default/gc_thresh3 - INTEGER
Default: 1024
+neigh/default/gc_stale_time - INTEGER
+ Determines how long a neighbor entry can remain unused before it is
+ considered stale and eligible for garbage collection. Entries that have
+ not been used for longer than this time will be removed by the garbage
+ collector, unless they have active references, are marked as PERMANENT,
+ or carry the NTF_EXT_LEARNED or NTF_EXT_VALIDATED flag. Stale entries
+ are only removed by the periodic GC when there are at least gc_thresh1
+ neighbors in the table.
+
+ Default: 60 seconds
+
neigh/default/unres_qlen_bytes - INTEGER
The maximum number of bytes which may be used by packets
queued for each unresolved address by other network layers.
--
2.47.3
next reply other threads:[~2026-02-23 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 10:12 Gabriel Goller [this message]
2026-02-25 1:18 ` [PATCH net-next v2] docs: net: document neigh gc_stale_time sysctl Jakub Kicinski
2026-02-25 10:00 ` Gabriel Goller
2026-02-25 1:50 ` patchwork-bot+netdevbpf
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=20260223101257.47563-1-g.goller@proxmox.com \
--to=g.goller@proxmox.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skhan@linuxfoundation.org \
/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