aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTimo Teräs <timo.teras@iki.fi>2009-06-11 15:38:02 -0400
committerDavid S. Miller <davem@davemloft.net>2009-06-14 02:36:32 -0400
commite61a4b634a15c11725eac8e66b457ba411168c7f (patch)
treedd9a1110b4c434d4e767b7fb23d4ccb106783575
parent125bb8f5637bd653244728f734bcac218986d910 (diff)
ipv4: update ARPD help text
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>
-rw-r--r--net/ipv4/Kconfig35
1 files changed, 13 insertions, 22 deletions
diff --git a/net/ipv4/Kconfig b/net/ipv4/Kconfig
index 5b919f7b45db..70491d9035eb 100644
--- a/net/ipv4/Kconfig
+++ b/net/ipv4/Kconfig
@@ -273,29 +273,20 @@ config IP_PIMSM_V2
273 you want to play with it. 273 you want to play with it.
274 274
275config ARPD 275config ARPD
276 bool "IP: ARP daemon support (EXPERIMENTAL)" 276 bool "IP: ARP daemon support"
277 depends on EXPERIMENTAL
278 ---help--- 277 ---help---
279 Normally, the kernel maintains an internal cache which maps IP 278 The kernel maintains an internal cache which maps IP addresses to
280 addresses to hardware addresses on the local network, so that 279 hardware addresses on the local network, so that Ethernet/Token Ring/
281 Ethernet/Token Ring/ etc. frames are sent to the proper address on 280 etc. frames are sent to the proper address on the physical networking
282 the physical networking layer. For small networks having a few 281 layer. Normally, kernel uses the ARP protocol to resolve these
283 hundred directly connected hosts or less, keeping this address 282 mappings.
284 resolution (ARP) cache inside the kernel works well. However, 283
285 maintaining an internal ARP cache does not work well for very large 284 Saying Y here adds support to have an user space daemon to do this
286 switched networks, and will use a lot of kernel memory if TCP/IP 285 resolution instead. This is useful for implementing an alternate
287 connections are made to many machines on the network. 286 address resolution protocol (e.g. NHRP on mGRE tunnels) and also for
288 287 testing purposes.
289 If you say Y here, the kernel's internal ARP cache will never grow 288
290 to more than 256 entries (the oldest entries are expired in a LIFO 289 If unsure, say N.
291 manner) and communication will be attempted with the user space ARP
292 daemon arpd. Arpd then answers the address resolution request either
293 from its own cache or by asking the net.
294
295 This code is experimental and also obsolete. If you want to use it,
296 you need to find a version of the daemon arpd on the net somewhere,
297 and you should also say Y to "Kernel/User network link driver",
298 below. If unsure, say N.
299 290
300config SYN_COOKIES 291config SYN_COOKIES
301 bool "IP: TCP syncookie support (disabled per default)" 292 bool "IP: TCP syncookie support (disabled per default)"