[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5a92f5cd-9af4-4228-dc44-b0c363f30e18@gmail.com>
Date: Wed, 13 Apr 2022 14:22:09 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Arun Ajith S <aajith@...sta.com>, netdev@...r.kernel.org
Cc: davem@...emloft.net, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, dsahern@...nel.org,
yoshfuji@...ux-ipv6.org, kuba@...nel.org, pabeni@...hat.com,
corbet@....net, prestwoj@...il.com, gilligan@...sta.com,
noureddine@...sta.com, gk@...sta.com
Subject: Re: [PATCH net-next v3] net/ipv6: Introduce accept_unsolicited_na
knob to implement router-side changes for RFC9131
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.
Powered by blists - more mailing lists