1. 26 4月, 2007 5 次提交
  2. 15 2月, 2007 1 次提交
    • T
      [PATCH] remove many unneeded #includes of sched.h · cd354f1a
      Tim Schmielau 提交于
      After Al Viro (finally) succeeded in removing the sched.h #include in module.h
      recently, it makes sense again to remove other superfluous sched.h includes.
      There are quite a lot of files which include it but don't actually need
      anything defined in there.  Presumably these includes were once needed for
      macros that used to live in sched.h, but moved to other header files in the
      course of cleaning it up.
      
      To ease the pain, this time I did not fiddle with any header files and only
      removed #includes from .c-files, which tend to cause less trouble.
      
      Compile tested against 2.6.20-rc2 and 2.6.20-rc2-mm2 (with offsets) on alpha,
      arm, i386, ia64, mips, powerpc, and x86_64 with allnoconfig, defconfig,
      allmodconfig, and allyesconfig as well as a few randconfigs on x86_64 and all
      configs in arch/arm/configs on arm.  I also checked that no new warnings were
      introduced by the patch (actually, some warnings are removed that were emitted
      by unnecessarily included header files).
      Signed-off-by: NTim Schmielau <tim@physik3.uni-rostock.de>
      Acked-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      cd354f1a
  3. 13 2月, 2007 1 次提交
  4. 11 2月, 2007 2 次提交
  5. 09 2月, 2007 1 次提交
    • P
      [NETLINK]: Don't BUG on undersized allocations · 26932566
      Patrick McHardy 提交于
      Currently netlink users BUG when the allocated skb for an event
      notification is undersized. While this is certainly a kernel bug,
      its not critical and crashing the kernel is too drastic, especially
      when considering that these errors have appeared multiple times in
      the past and it BUGs even if no listeners are present.
      
      This patch replaces BUG by WARN_ON and changes the notification
      functions to inform potential listeners of undersized allocations
      using a unique error code (EMSGSIZE).
      Signed-off-by: NPatrick McHardy <kaber@trash.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      26932566
  6. 18 12月, 2006 1 次提交
  7. 11 12月, 2006 1 次提交
  8. 07 12月, 2006 1 次提交
  9. 03 12月, 2006 4 次提交
  10. 12 10月, 2006 1 次提交
  11. 29 9月, 2006 7 次提交
  12. 23 9月, 2006 5 次提交
  13. 08 8月, 2006 1 次提交
    • K
      [IPV4]: Limit rt cache size properly. · 8d1502de
      Kirill Korotaev 提交于
      From: Kirill Korotaev <dev@sw.ru>
      
      During OpenVZ stress testing we found that UDP traffic with random src
      can generate too much excessive rt hash growing leading finally to OOM
      and kernel panics.
      
      It was found that for 4GB i686 system (having 1048576 total pages and
        225280 normal zone pages) kernel allocates the following route hash:
      syslog: IP route cache hash table entries: 262144 (order: 8, 1048576
      bytes) => ip_rt_max_size = 4194304 entries, i.e.  max rt size is
      4194304 * 256b = 1Gb of RAM > normal_zone
      
      Attached the patch which removes HASH_HIGHMEM flag from
      alloc_large_system_hash() call.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      8d1502de
  14. 03 8月, 2006 1 次提交
  15. 04 7月, 2006 2 次提交
  16. 01 7月, 2006 1 次提交
  17. 26 6月, 2006 1 次提交
  18. 18 4月, 2006 1 次提交
  19. 11 4月, 2006 1 次提交
  20. 25 3月, 2006 1 次提交
    • I
      [IPV4]: Aggregate route entries with different TOS values · cef2685e
      Ilia Sotnikov 提交于
      When we get an ICMP need-to-frag message, the original TOS value in the
      ICMP payload cannot be used as a key to look up the routes to update.
      This is because the TOS field may have been modified by routers on the
      way.  Similarly, ip_rt_redirect should also ignore the TOS as the router
      that gave us the message may have modified the TOS value.
      
      The patch achieves this objective by aggregating entries with different
      TOS values (but are otherwise identical) into the same bucket.  This
      makes it easy to update them at the same time when an ICMP message is
      received.
      
      In future we should use a twin-hashing scheme where teh aggregation
      occurs at the entry level.  That is, the TOS goes back into the hash
      for normal lookups while ICMP lookups will end up with a node that
      gives us a list that contains all other route entries that differ
      only by TOS.
      Signed-off-by: NIlia Sotnikov <hostcc@gmail.com>
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      cef2685e
  21. 24 2月, 2006 1 次提交