net: doc: add default value for neighbour parameters
Subsystems (3)
PATCH 2/2 net: doc: add default value for neighbour parameters
From: Shan Wei <[email protected]>
--- Documentation/networking/ip-sysctl.txt | 8 ++++++++ 1 files changed, 8 insertions(+), 0 deletions(-)
Documentation/networking/ip-sysctl.txt +8 -0
@@ -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.
Signature · 1 line
1.7.1
From: Shan Wei <[email protected]>
Date: Wed, 05 Dec 2012 12:50:35 +0800
Quoted 3 lines
From: Shan Wei <[email protected]>
Signed-off-by Shan Wei <[email protected]>
Applied.
Quoted 20 lines · Shan Wei
From: Shan Wei <[email protected]>
Signed-off-by Shan Wei <[email protected]>--- Documentation/networking/ip-sysctl.txt | 8 ++++++++ 1 files changed, 8 insertions(+), 0 deletions(-)Documentation/networking/ip-sysctl.txt +1
-0@@ -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.
Documentation/networking/ip-sysctl.txt neigh/default/gc_thresh3 - INTEGER · line 47
Quoted 10 lines
Documentation/networking/ip-sysctl.txt +4
-0(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'?
Quoted 6 lines
Documentation/networking/ip-sysctl.txt +3
-0+ 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.
Signature · 3 lines
Ben Hutchings, Staff Engineer, Solarflare Not speaking for my employer; that's the marketing department's job. They asked us to note that Solarflare product names are trademarked.
Ben Hutchings said, at 2012/12/6 9:43:
Quoted 8 lines
Documentation/networking/ip-sysctl.txt neigh/default/gc_thresh3 - INTEGER · line 47
Quoted 6 lines
neigh/default/unres_qlen - INTEGER
Documentation/networking/ip-sysctl.txt +2
-0The 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
Quoted 16 lines · Shan Wei
Ben Hutchings said, at 2012/12/6 9:43:
Quoted 8 lines
Documentation/networking/ip-sysctl.txt neigh/default/gc_thresh3 - INTEGER · line 47
Quoted 6 lines
neigh/default/unres_qlen - INTEGER
Documentation/networking/ip-sysctl.txt +2
-0The 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_discardsof/proc/net/stat/arp_cache. Although,arp_cacheis not easy to understand(I still don't know why we need so many rows), We can confirm dropping event fromunresolved_discardsin last column. The dropping event is not marked by absence of sound.
Quoted 7 lines
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.
Signature · 3 lines
Ben Hutchings, Staff Engineer, Solarflare Not speaking for my employer; that's the marketing department's job. They asked us to note that Solarflare product names are trademarked.
Ben Hutchings said, at 2012/12/7 4:20:
Quoted 4 lines
'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.
You are right，good suggestion :-).
Thanks for your review.
-------------------------
[PATCH net-next] net: doc : use more suitable word 'unexpected' to replace 'secluded'
'secluded' is used to describe places, not suitable here.
--- Documentation/networking/ip-sysctl.txt | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
Documentation/networking/ip-sysctl.txt +1 -1
@@ -44,7 +44,7 @@ neigh/default/unres_qlen - INTEGER 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 + unexpected packet loss. The current default value is calculated according to default value of unres_qlen_bytes and true size of packet. Default: 31
Signature · 1 line
1.7.1
From: Shan Wei <[email protected]>
Date: Fri, 07 Dec 2012 10:27:51 +0800
Quoted 6 lines
[PATCH net-next] net: doc : use more suitable word 'unexpected' to replace 'secluded'
'secluded' is used to describe places, not suitable here.
Suggested-by Ben Hutchings <[email protected]>Signed-off-by Shan Wei <[email protected]>
Applied.