1. 01 11月, 2013 1 次提交
  2. 28 10月, 2013 1 次提交
    • S
      xfrm: Increase the garbage collector threshold · eeb1b733
      Steffen Klassert 提交于
      With the removal of the routing cache, we lost the
      option to tweak the garbage collector threshold
      along with the maximum routing cache size. So git
      commit 703fb94e ("xfrm: Fix the gc threshold value
      for ipv4") moved back to a static threshold.
      
      It turned out that the current threshold before we
      start garbage collecting is much to small for some
      workloads, so increase it from 1024 to 32768. This
      means that we start the garbage collector if we have
      more than 32768 dst entries in the system and refuse
      new allocations if we are above 65536.
      Reported-by: NWolfgang Walter <linux@stwm.de>
      Signed-off-by: NSteffen Klassert <steffen.klassert@secunet.com>
      eeb1b733
  3. 16 9月, 2013 1 次提交
  4. 06 2月, 2013 2 次提交
  5. 13 11月, 2012 1 次提交
  6. 09 10月, 2012 1 次提交
    • J
      ipv4: introduce rt_uses_gateway · 155e8336
      Julian Anastasov 提交于
      Add new flag to remember when route is via gateway.
      We will use it to allow rt_gateway to contain address of
      directly connected host for the cases when DST_NOCACHE is
      used or when the NH exception caches per-destination route
      without DST_NOCACHE flag, i.e. when routes are not used for
      other destinations. By this way we force the neighbour
      resolving to work with the routed destination but we
      can use different address in the packet, feature needed
      for IPVS-DR where original packet for virtual IP is routed
      via route to real IP.
      Signed-off-by: NJulian Anastasov <ja@ssi.bg>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      155e8336
  7. 01 8月, 2012 1 次提交
  8. 21 7月, 2012 6 次提交
  9. 17 7月, 2012 1 次提交
    • D
      net: Pass optional SKB and SK arguments to dst_ops->{update_pmtu,redirect}() · 6700c270
      David S. Miller 提交于
      This will be used so that we can compose a full flow key.
      
      Even though we have a route in this context, we need more.  In the
      future the routes will be without destination address, source address,
      etc. keying.  One ipv4 route will cover entire subnets, etc.
      
      In this environment we have to have a way to possess persistent storage
      for redirects and PMTU information.  This persistent storage will exist
      in the FIB tables, and that's why we'll need to be able to rebuild a
      full lookup flow key here.  Using that flow key will do a fib_lookup()
      and create/update the persistent entry.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6700c270
  10. 12 7月, 2012 2 次提交
  11. 11 7月, 2012 2 次提交
  12. 28 6月, 2012 1 次提交
  13. 11 6月, 2012 1 次提交
  14. 21 4月, 2012 1 次提交
  15. 16 4月, 2012 1 次提交
  16. 24 10月, 2011 1 次提交
  17. 22 6月, 2011 1 次提交
  18. 11 5月, 2011 1 次提交
  19. 04 5月, 2011 1 次提交
  20. 23 4月, 2011 1 次提交
  21. 08 4月, 2011 1 次提交
  22. 13 3月, 2011 5 次提交
  23. 05 3月, 2011 1 次提交
  24. 03 3月, 2011 1 次提交
  25. 02 3月, 2011 1 次提交
  26. 24 2月, 2011 1 次提交
  27. 23 2月, 2011 2 次提交