Message ID | 50BED29B.4050805@gmail.com |
---|---|
State | Accepted, archived |
Delegated to: | David Miller |
Headers | show |
From: Shan Wei <shanwei88@gmail.com> Date: Wed, 05 Dec 2012 12:50:35 +0800 > From: Shan Wei <davidshan@tencent.com> > > Signed-off-by: Shan Wei <davidshan@tencent.com> Applied. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, 2012-12-05 at 12:50 +0800, Shan Wei wrote: > From: Shan Wei <davidshan@tencent.com> > > Signed-off-by: Shan Wei <davidshan@tencent.com> > --- > Documentation/networking/ip-sysctl.txt | 8 ++++++++ > 1 files changed, 8 insertions(+), 0 deletions(-) > > diff --git a/Documentation/networking/ip-sysctl.txt b/Documentation/networking/ip-sysctl.txt > index c6d5fee..0462a71 100644 > --- a/Documentation/networking/ip-sysctl.txt > +++ b/Documentation/networking/ip-sysctl.txt > @@ -30,16 +30,24 @@ neigh/default/gc_thresh3 - INTEGER > Maximum number of neighbor entries allowed. Increase this > when using large numbers of interfaces and when communicating > with large numbers of directly-connected peers. > + Default: 1024 > > neigh/default/unres_qlen_bytes - INTEGER > The maximum number of bytes which may be used by packets > queued for each unresolved address by other network layers. > (added in linux 3.3) > + Seting negative value is meaningless and will retrun error. > + Default: 65536 Bytes(64KB) > > 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'? > + according to default value of unres_qlen_bytes and true size of > + packet. > + Default: 31 > > mtu_expires - INTEGER > Time, in seconds, that cached PMTU information is kept.
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 -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, 2012-12-06 at 10:58 +0800, Shan Wei wrote: > 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. 'Secluded' is a fine word but your dictionary should have said that it is used to describe places, not events. You're quite right that this is not silent, though. So a word like 'hidden', 'quiet', 'non-obvious' or 'unexpected' would be more appropriate. Ben.
diff --git a/Documentation/networking/ip-sysctl.txt b/Documentation/networking/ip-sysctl.txt index c6d5fee..0462a71 100644 --- a/Documentation/networking/ip-sysctl.txt +++ b/Documentation/networking/ip-sysctl.txt @@ -30,16 +30,24 @@ neigh/default/gc_thresh3 - INTEGER Maximum number of neighbor entries allowed. Increase this when using large numbers of interfaces and when communicating with large numbers of directly-connected peers. + Default: 1024 neigh/default/unres_qlen_bytes - INTEGER The maximum number of bytes which may be used by packets queued for each unresolved address by other network layers. (added in linux 3.3) + Seting negative value is meaningless and will retrun error. + Default: 65536 Bytes(64KB) 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 + according to default value of unres_qlen_bytes and true size of + packet. + Default: 31 mtu_expires - INTEGER Time, in seconds, that cached PMTU information is kept.