1. 14 6月, 2009 1 次提交
    • T
      ipv4: update ARPD help text · e61a4b63
      Timo Teräs 提交于
      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: NTimo Teras <timo.teras@iki.fi>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      e61a4b63
  2. 19 5月, 2009 1 次提交
  3. 09 5月, 2009 1 次提交
  4. 24 2月, 2009 1 次提交
  5. 23 2月, 2009 2 次提交
  6. 07 10月, 2008 1 次提交
  7. 25 7月, 2008 1 次提交
  8. 12 4月, 2008 1 次提交
  9. 07 3月, 2008 1 次提交
    • D
      [UDP]: Revert udplite and code split. · db8dac20
      David S. Miller 提交于
      This reverts commit db1ed684 ("[IPV6]
      UDP: Rename IPv6 UDP files."), commit
      8be8af8f ("[IPV4] UDP: Move
      IPv4-specific bits to other file.") and commit
      e898d4db ("[UDP]: Allow users to
      configure UDP-Lite.").
      
      First, udplite is of such small cost, and it is a core protocol just
      like TCP and normal UDP are.
      
      We spent enormous amounts of effort to make udplite share as much code
      with core UDP as possible.  All of that work is less valuable if we're
      just going to slap a config option on udplite support.
      
      It is also causing build failures, as reported on linux-next, showing
      that the changeset was not tested very well.  In fact, this is the
      second build failure resulting from the udplite change.
      
      Finally, the config options provided was a bool, instead of a modular
      option.  Meaning the udplite code does not even get build tested
      by allmodconfig builds, and furthermore the user is not presented
      with a reasonable modular build option which is particularly needed
      by distribution vendors.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      db8dac20
  10. 05 3月, 2008 1 次提交
  11. 04 3月, 2008 1 次提交
    • Y
      [UDP]: Allow users to configure UDP-Lite. · e898d4db
      YOSHIFUJI Hideaki 提交于
      Let's give users an option for disabling UDP-Lite (~4K).
      
      old:
      |    text	   data	    bss	    dec	    hex	filename
      |  286498	  12432	   6072	 305002	  4a76a	net/ipv4/built-in.o
      |  193830	   8192	   3204	 205226	  321aa	net/ipv6/ipv6.o
      
      new (without UDP-Lite):
      |    text	   data	    bss	    dec	    hex	filename
      |  284086	  12136	   5432	 301654	  49a56	net/ipv4/built-in.o
      |  191835	   7832	   3076	 202743	  317f7	net/ipv6/ipv6.o
      Signed-off-by: NYOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
      e898d4db
  12. 01 2月, 2008 1 次提交
  13. 29 1月, 2008 1 次提交
  14. 20 10月, 2007 1 次提交
  15. 11 10月, 2007 1 次提交
  16. 11 7月, 2007 1 次提交
  17. 18 5月, 2007 2 次提交
  18. 09 5月, 2007 1 次提交
  19. 26 4月, 2007 2 次提交
  20. 27 2月, 2007 1 次提交
  21. 18 2月, 2007 1 次提交
  22. 03 12月, 2006 3 次提交
  23. 04 10月, 2006 3 次提交
  24. 25 9月, 2006 2 次提交
  25. 23 9月, 2006 1 次提交
  26. 21 9月, 2006 1 次提交
  27. 11 7月, 2006 1 次提交
  28. 18 6月, 2006 4 次提交
  29. 29 3月, 2006 1 次提交
    • H
      [INET]: Introduce tunnel4/tunnel6 · d2acc347
      Herbert Xu 提交于
      Basically this patch moves the generic tunnel protocol stuff out of
      xfrm4_tunnel/xfrm6_tunnel and moves it into the new files of tunnel4.c
      and tunnel6 respectively.
      
      The reason for this is that the problem that Hugo uncovered is only
      the tip of the iceberg.  The real problem is that when we removed the
      dependency of ipip on xfrm4_tunnel we didn't really consider the module
      case at all.
      
      For instance, as it is it's possible to build both ipip and xfrm4_tunnel
      as modules and if the latter is loaded then ipip simply won't load.
      
      After considering the alternatives I've decided that the best way out of
      this is to restore the dependency of ipip on the non-xfrm-specific part
      of xfrm4_tunnel.  This is acceptable IMHO because the intention of the
      removal was really to be able to use ipip without the xfrm subsystem.
      This is still preserved by this patch.
      
      So now both ipip/xfrm4_tunnel depend on the new tunnel4.c which handles
      the arbitration between the two.  The order of processing is determined
      by a simple integer which ensures that ipip gets processed before
      xfrm4_tunnel.
      
      The situation for ICMP handling is a little bit more complicated since
      we may not have enough information to determine who it's for.  It's not
      a big deal at the moment since the xfrm ICMP handlers are basically
      no-ops.  In future we can deal with this when we look at ICMP caching
      in general.
      
      The user-visible change to this is the removal of the TUNNEL Kconfig
      prompts.  This makes sense because it can only be used through IPCOMP
      as it stands.
      
      The addition of the new modules shouldn't introduce any problems since
      module dependency will cause them to be loaded.
      
      Oh and I also turned some unnecessary pskb's in IPv6 related to this
      patch to skb's.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      d2acc347