From: Bagas Sanjaya <bagasdotme@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 v6] net/ipv6: Introduce accept_unsolicited_na knob to implement router-side changes for RFC9131
Date: Sat, 16 Apr 2022 12:43:14 +0700 [thread overview]
Message-ID: <642672cb-8b11-c78f-8975-f287ece9e89e@gmail.com> (raw)
In-Reply-To: <20220415083402.39080-1-aajith@arista.com>
On 4/15/22 15:34, Arun Ajith S wrote:
> +accept_unsolicited_na - BOOLEAN
> + Add a new neighbour cache entry in STALE state for routers on receiving an
> + unsolicited neighbour advertisement with target link-layer address option
> + specified. This is as per router-side behavior documented in RFC9131.
> + This has lower precedence than drop_unsolicited_na.
> +
> + ==== ====== ====== ==============================================
> + drop accept fwding behaviour
> + ---- ------ ------ ----------------------------------------------
> + 1 X X Drop NA packet and don't pass up the stack
> + 0 0 X Pass NA packet up the stack, don't update NC
> + 0 1 0 Pass NA packet up the stack, don't update NC
> + 0 1 1 Pass NA packet up the stack, and add a STALE
> + NC entry
> + ==== ====== ====== ==============================================
> +
> + This will optimize the return path for the initial off-link communication
> + that is initiated by a directly connected host, by ensuring that
> + the first-hop router which turns on this setting doesn't have to
> + buffer the initial return packets to do neighbour-solicitation.
> + The prerequisite is that the host is configured to send
> + unsolicited neighbour advertisements on interface bringup.
> + This setting should be used in conjunction with the ndisc_notify setting
> + on the host to satisfy this prerequisite.
> +
> + By default this is turned off.
> +
Looks good. htmldocs builds successfully and the table displayed properly.
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
However, I remind you the following:
- The patch changelogs should be put between the dashes (---) and diffstat.
I don't see the changelogs when I hit reply-all because you put them as
message signature (at very bottom of patch message).
- DON'T DO top-posting, DO configure your MUA to make reply text below
the quoted text instead.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-04-16 5:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 8:34 Arun Ajith S
2022-04-16 5:43 ` Bagas Sanjaya [this message]
2022-04-16 12:20 ` Arun Ajith S
2022-04-17 12:30 ` 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=642672cb-8b11-c78f-8975-f287ece9e89e@gmail.com \
--to=bagasdotme@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
all inboxes | Powered by JetHome®