[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1321584035715@vla5-ac90c725e5c1.qloud-c.yandex.net>
Date: Thu, 12 Mar 2020 21:02:33 +0300
From: Aleksei Zakharov <zakharov.a.g@...dex.ru>
To: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH] man: fix lnstat unresolved_discards description
Hi all,
Could this be submitted or am i missing something?
lnstat's unresolved_discards field description looks unclear, as for me.
And from the code it looks like it's a counter of dropped packets,
not table entries, unless i'm not mistaken.
02.03.2020, 14:54, "Aleksei Zakharov" <zakharov.a.g@...dex.ru>:
> Signed-off-by: Aleksei Zakharov <zakharov.a.g@...dex.ru>
> ---
> man/man8/lnstat.8 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man/man8/lnstat.8 b/man/man8/lnstat.8
> index b98241bf..f25a9623 100644
> --- a/man/man8/lnstat.8
> +++ b/man/man8/lnstat.8
> @@ -121,7 +121,7 @@ How many forced garbage collection runs were executed. Happens when adding an
> entry and the table is too full.
> .sp
> .B unresolved_discards
> -How many neighbor table entries were discarded due to lookup failure.
> +How many packets were discarded due to lookup failure and arp queue overfill.
> .sp
> .B table_fulls
> Number of table overflows. Happens if table is full and forced GC run (see
> --
> 2.17.1
--
Regards,
Aleksei Zakharov
Powered by blists - more mailing lists