1. 12 11月, 2014 1 次提交
  2. 10 12月, 2013 1 次提交
  3. 19 2月, 2013 2 次提交
  4. 11 2月, 2013 1 次提交
  5. 05 7月, 2012 1 次提交
  6. 04 6月, 2012 1 次提交
  7. 16 5月, 2012 1 次提交
  8. 02 2月, 2012 1 次提交
  9. 29 12月, 2011 1 次提交
  10. 06 12月, 2011 1 次提交
  11. 14 11月, 2011 1 次提交
    • E
      neigh: new unresolved queue limits · 8b5c171b
      Eric Dumazet 提交于
      Le mercredi 09 novembre 2011 à 16:21 -0500, David Miller a écrit :
      > From: David Miller <davem@davemloft.net>
      > Date: Wed, 09 Nov 2011 16:16:44 -0500 (EST)
      >
      > > From: Eric Dumazet <eric.dumazet@gmail.com>
      > > Date: Wed, 09 Nov 2011 12:14:09 +0100
      > >
      > >> unres_qlen is the number of frames we are able to queue per unresolved
      > >> neighbour. Its default value (3) was never changed and is responsible
      > >> for strange drops, especially if IP fragments are used, or multiple
      > >> sessions start in parallel. Even a single tcp flow can hit this limit.
      > >  ...
      > >
      > > Ok, I've applied this, let's see what happens :-)
      >
      > Early answer, build fails.
      >
      > Please test build this patch with DECNET enabled and resubmit.  The
      > decnet neigh layer still refers to the removed ->queue_len member.
      >
      > Thanks.
      
      Ouch, this was fixed on one machine yesterday, but not the other one I
      used this morning, sorry.
      
      [PATCH V5 net-next] neigh: new unresolved queue limits
      
      unres_qlen is the number of frames we are able to queue per unresolved
      neighbour. Its default value (3) was never changed and is responsible
      for strange drops, especially if IP fragments are used, or multiple
      sessions start in parallel. Even a single tcp flow can hit this limit.
      
      $ arp -d 192.168.20.108 ; ping -c 2 -s 8000 192.168.20.108
      PING 192.168.20.108 (192.168.20.108) 8000(8028) bytes of data.
      8008 bytes from 192.168.20.108: icmp_seq=2 ttl=64 time=0.322 ms
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      8b5c171b
  12. 27 7月, 2011 1 次提交
  13. 18 7月, 2011 2 次提交
  14. 17 7月, 2011 2 次提交
  15. 02 7月, 2011 1 次提交
  16. 09 11月, 2010 1 次提交
  17. 06 10月, 2010 1 次提交
    • E
      net neigh: RCU conversion of neigh hash table · d6bf7817
      Eric Dumazet 提交于
      David
      
      This is the first step for RCU conversion of neigh code.
      
      Next patches will convert hash_buckets[] and "struct neighbour" to RCU
      protected objects.
      
      Thanks
      
      [PATCH net-next] net neigh: RCU conversion of neigh hash table
      
      Instead of storing hash_buckets, hash_mask and hash_rnd in "struct
      neigh_table", a new structure is defined :
      
      struct neigh_hash_table {
             struct neighbour        **hash_buckets;
             unsigned int            hash_mask;
             __u32                   hash_rnd;
             struct rcu_head         rcu;
      };
      
      And "struct neigh_table" has an RCU protected pointer to such a
      neigh_hash_table.
      
      This means the signature of (*hash)() function changed: We need to add a
      third parameter with the actual hash_rnd value, since this is not
      anymore a neigh_table field.
      Signed-off-by: NEric Dumazet <eric.dumazet@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      d6bf7817
  18. 30 3月, 2010 1 次提交
    • T
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo 提交于
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
      
      percpu.h is included by sched.h and module.h and thus ends up being
      included when building most .c files.  percpu.h includes slab.h which
      in turn includes gfp.h making everything defined by the two files
      universally available and complicating inclusion dependencies.
      
      percpu.h -> slab.h dependency is about to be removed.  Prepare for
      this change by updating users of gfp and slab facilities include those
      headers directly instead of assuming availability.  As this conversion
      needs to touch large number of source files, the following script is
      used as the basis of conversion.
      
        http://userweb.kernel.org/~tj/misc/slabh-sweep.py
      
      The script does the followings.
      
      * Scan files for gfp and slab usages and update includes such that
        only the necessary includes are there.  ie. if only gfp is used,
        gfp.h, if slab is used, slab.h.
      
      * When the script inserts a new include, it looks at the include
        blocks and try to put the new include such that its order conforms
        to its surrounding.  It's put in the include block which contains
        core kernel includes, in the same order that the rest are ordered -
        alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
        doesn't seem to be any matching order.
      
      * If the script can't find a place to put a new include (mostly
        because the file doesn't have fitting include block), it prints out
        an error message indicating which .h file needs to be added to the
        file.
      
      The conversion was done in the following steps.
      
      1. The initial automatic conversion of all .c files updated slightly
         over 4000 files, deleting around 700 includes and adding ~480 gfp.h
         and ~3000 slab.h inclusions.  The script emitted errors for ~400
         files.
      
      2. Each error was manually checked.  Some didn't need the inclusion,
         some needed manual addition while adding it to implementation .h or
         embedding .c file was more appropriate for others.  This step added
         inclusions to around 150 files.
      
      3. The script was run again and the output was compared to the edits
         from #2 to make sure no file was left behind.
      
      4. Several build tests were done and a couple of problems were fixed.
         e.g. lib/decompress_*.c used malloc/free() wrappers around slab
         APIs requiring slab.h to be added manually.
      
      5. The script was run on all .h files but without automatically
         editing them as sprinkling gfp.h and slab.h inclusions around .h
         files could easily lead to inclusion dependency hell.  Most gfp.h
         inclusion directives were ignored as stuff from gfp.h was usually
         wildly available and often used in preprocessor macros.  Each
         slab.h inclusion directive was examined and added manually as
         necessary.
      
      6. percpu.h was updated not to include slab.h.
      
      7. Build test were done on the following configurations and failures
         were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
         distributed build env didn't work with gcov compiles) and a few
         more options had to be turned off depending on archs to make things
         build (like ipr on powerpc/64 which failed due to missing writeq).
      
         * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
         * powerpc and powerpc64 SMP allmodconfig
         * sparc and sparc64 SMP allmodconfig
         * ia64 SMP allmodconfig
         * s390 SMP allmodconfig
         * alpha SMP allmodconfig
         * um on x86_64 SMP allmodconfig
      
      8. percpu.h modifications were reverted so that it could be applied as
         a separate patch and serve as bisection point.
      
      Given the fact that I had only a couple of failures from tests on step
      6, I'm fairly confident about the coverage of this conversion patch.
      If there is a breakage, it's likely to be something in one of the arch
      headers which should be easily discoverable easily on most builds of
      the specific arch.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Guess-its-ok-by: NChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
      5a0e3ad6
  19. 25 3月, 2010 1 次提交
  20. 02 9月, 2009 1 次提交
  21. 03 6月, 2009 1 次提交
  22. 27 11月, 2008 1 次提交
  23. 29 1月, 2008 1 次提交
    • E
      [NETNS]: Modify the neighbour table code so it handles multiple network namespaces · 426b5303
      Eric W. Biederman 提交于
      I'm actually surprised at how much was involved.  At first glance it
      appears that the neighbour table data structures are already split by
      network device so all that should be needed is to modify the user
      interface commands to filter the set of neighbours by the network
      namespace of their devices.
      
      However a couple things turned up while I was reading through the
      code.  The proxy neighbour table allows entries with no network
      device, and the neighbour parms are per network device (except for the
      defaults) so they now need a per network namespace default.
      
      So I updated the two structures (which surprised me) with their very
      own network namespace parameter.  Updated the relevant lookup and
      destroy routines with a network namespace parameter and modified the
      code that interacts with users to filter out neighbour table entries
      for devices of other namespaces.
      
      I'm a little concerned that we can modify and display the global table
      configuration and from all network namespaces.  But this appears good
      enough for now.
      
      I keep thinking modifying the neighbour table to have per network
      namespace instances of each table type would should be cleaner.  The
      hash table is already dynamically sized so there are it is not a
      limiter.  The default parameter would be straight forward to take care
      of.  However when I look at the how the network table is built and
      used I still find some assumptions that there is only a single
      neighbour table for each type of table in the kernel.  The netlink
      operations, neigh_seq_start, the non-core network users that call
      neigh_lookup.  So while it might be doable it would require more
      refactoring than my current approach of just doing a little extra
      filtering in the code.
      Signed-off-by: NEric W. Biederman <ebiederm@xmission.com>
      Signed-off-by: NDaniel Lezcano <dlezcano@fr.ibm.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      426b5303
  24. 11 10月, 2007 3 次提交
  25. 11 7月, 2007 1 次提交
  26. 26 4月, 2007 1 次提交
  27. 13 2月, 2007 1 次提交
  28. 11 2月, 2007 1 次提交
  29. 03 12月, 2006 1 次提交
  30. 22 7月, 2006 1 次提交
  31. 01 7月, 2006 1 次提交
  32. 04 5月, 2006 1 次提交
  33. 21 3月, 2006 1 次提交
    • S
      [DECnet]: Endian annotation and fixes for DECnet. · c4ea94ab
      Steven Whitehouse 提交于
      The typedef for dn_address has been removed in favour of using __le16
      or __u16 directly as appropriate. All the DECnet header files are
      updated accordingly.
      
      The byte ordering of dn_eth2dn() and dn_dn2eth() are both changed
      since just about all their callers wanted network order rather than
      host order, so the conversion is now done in the functions themselves.
      
      Several missed endianess conversions have been picked up during the
      conversion process. The nh_gw field in struct dn_fib_info has been
      changed from a 32 bit field to 16 bits as it ought to be.
      
      One or two cases of using htons rather than dn_htons in the routing
      code have been found and fixed.
      
      There are still a few warnings to fix, but this patch deals with the
      important cases.
      Signed-off-by: NSteven Whitehouse <steve@chygwyn.com>
      Signed-off-by: NPatrick Caulfield <patrick@tykepenguin.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      c4ea94ab
  34. 04 1月, 2006 1 次提交
  35. 18 8月, 2005 1 次提交