Techwizz/kernel-fxtec-pro1x
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

ipv4: update ARPD help text

Browse source 
Removed the statements about ARP cache size as this config option does
not affect it. The cache size is controlled by neigh_table gc thresholds.

Remove also expiremental and obsolete markings as the API originally
intended for arp caching is useful for implementing ARP-like protocols
(e.g. NHRP) in user space and has been there for a long enough time.

Signed-off-by: Timo Teras <timo.teras@iki.fi>
Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
Timo Teräs 2009-06-11 19:38:02 +00:00 committed by David S. Miller
parent 125bb8f563
commit e61a4b634a
1 changed files with 11 additions and 20 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

31
net/ipv4/Kconfig
View file

@ -273,29 +273,20 @@ config IP_PIMSM_V2
you want to play with it.
config ARPD
bool "IP: ARP daemon support (EXPERIMENTAL)"
depends on EXPERIMENTAL
bool "IP: ARP daemon support"
---help---
Normally, the kernel maintains an internal cache which maps IP
addresses to hardware addresses on the local network, so that
Ethernet/Token Ring/ etc. frames are sent to the proper address on
the physical networking layer. For small networks having a few
hundred directly connected hosts or less, keeping this address
resolution (ARP) cache inside the kernel works well. However,
maintaining an internal ARP cache does not work well for very large
switched networks, and will use a lot of kernel memory if TCP/IP
connections are made to many machines on the network.
The kernel maintains an internal cache which maps IP addresses to
hardware addresses on the local network, so that Ethernet/Token Ring/
etc. frames are sent to the proper address on the physical networking
layer. Normally, kernel uses the ARP protocol to resolve these
mappings.
If you say Y here, the kernel's internal ARP cache will never grow
to more than 256 entries (the oldest entries are expired in a LIFO
manner) and communication will be attempted with the user space ARP
daemon arpd. Arpd then answers the address resolution request either
from its own cache or by asking the net.
Saying Y here adds support to have an user space daemon to do this
resolution instead. This is useful for implementing an alternate
address resolution protocol (e.g. NHRP on mGRE tunnels) and also for
testing purposes.
This code is experimental and also obsolete. If you want to use it,
you need to find a version of the daemon arpd on the net somewhere,
and you should also say Y to "Kernel/User network link driver",
below. If unsure, say N.
If unsure, say N.
config SYN_COOKIES
bool "IP: TCP syncookie support (disabled per default)"