From: Shan Wei <shanwei88@gmail.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: David Miller <davem@davemloft.net>,
Eric Dumazet <eric.dumazet@gmail.com>,
NetDev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 2/2] net: doc: add default value for neighbour parameters
Date: Thu, 06 Dec 2012 10:58:49 +0800 [thread overview]
Message-ID: <50C009E9.6050101@gmail.com> (raw)
In-Reply-To: <1354758235.17107.131.camel@deadeye.wl.decadent.org.uk>
Ben Hutchings said, at 2012/12/6 9:43:
>> neigh/default/unres_qlen - INTEGER
>> The maximum number of packets which may be queued for each
>> unresolved address by other network layers.
>> (deprecated in linux 3.3) : use unres_qlen_bytes instead.
>> + Prior to linux 3.3, the default value is 3 which may cause
>> + secluded packet loss. The current default value is calculated
> ^^^^^^^^
> I think the proper word here is 'silent'?
The number of lost packets is recorded in unresolved_discards
of /proc/net/stat/arp_cache. Although, arp_cache is not easy
to understand(I still don't know why we need so many rows),
We can confirm dropping event from unresolved_discards in last column.
The dropping event is not marked by absence of sound.
But for general user who using TCP/UDP or ping to sending packets
out, can't simply find the dropping reason that destination ip is unresolved.
They just doubt about the TCP/UDP or ping. So I use 'secluded' which is hidden
from general view.
My English is not good enough, if missing something, please point to me.
Thanks.
Best Regards
Shan Wei
next prev parent reply other threads:[~2012-12-06 2:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 4:50 [PATCH net-next 2/2] net: doc: add default value for neighbour parameters Shan Wei
2012-12-05 21:26 ` David Miller
2012-12-06 1:43 ` Ben Hutchings
2012-12-06 2:58 ` Shan Wei [this message]
2012-12-06 20:20 ` Ben Hutchings
2012-12-07 2:27 ` Shan Wei
2012-12-07 19:31 ` David Miller
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=50C009E9.6050101@gmail.com \
--to=shanwei88@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.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).