From: Eric Dumazet <eric.dumazet@gmail.com>
To: Arun Ajith S <aajith@arista.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, dsahern@kernel.org,
yoshfuji@linux-ipv6.org, kuba@kernel.org, pabeni@redhat.com,
corbet@lwn.net, prestwoj@gmail.com, gilligan@arista.com,
noureddine@arista.com, gk@arista.com
Subject: Re: [PATCH net-next v3] net/ipv6: Introduce accept_unsolicited_na knob to implement router-side changes for RFC9131
Date: Wed, 13 Apr 2022 14:22:09 -0700 [thread overview]
Message-ID: <5a92f5cd-9af4-4228-dc44-b0c363f30e18@gmail.com> (raw)
In-Reply-To: <20220413143434.527-1-aajith@arista.com>
On 4/13/22 07:34, Arun Ajith S wrote:
> Add a new neighbour cache entry in STALE state for routers on receiving
> an unsolicited (gratuitous) neighbour advertisement with
> target link-layer-address option specified.
> This is similar to the arp_accept configuration for IPv4.
> A new sysctl endpoint is created to turn on this behaviour:
> /proc/sys/net/ipv6/conf/interface/accept_unsolicited_na.
Do we really need to expose this to /proc/sys, for every interface added
in the host ?
/proc files creations/deletion cost a lot in environments
adding/deleting netns very often.
I would prefer using NETLINK attributes, a single recvmsg() syscall can
fetch/set hundreds of them.
next prev parent reply other threads:[~2022-04-13 21:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 14:34 [PATCH net-next v3] net/ipv6: Introduce accept_unsolicited_na knob to implement router-side changes for RFC9131 Arun Ajith S
2022-04-13 21:22 ` Eric Dumazet [this message]
2022-04-13 22:00 ` David Ahern
2022-04-13 22:03 ` Eric Dumazet
2022-04-13 22:07 ` David Ahern
2022-05-20 7:19 ` Arun Ajith S
2022-05-21 2:00 ` David Ahern
2022-05-27 7:35 ` Arun Ajith S
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=5a92f5cd-9af4-4228-dc44-b0c363f30e18@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=aajith@arista.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=gilligan@arista.com \
--cc=gk@arista.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noureddine@arista.com \
--cc=pabeni@redhat.com \
--cc=prestwoj@gmail.com \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).