1. 09 11月, 2011 1 次提交
  2. 01 11月, 2011 3 次提交
  3. 30 10月, 2011 1 次提交
  4. 20 10月, 2011 1 次提交
  5. 12 10月, 2011 1 次提交
  6. 07 10月, 2011 1 次提交
  7. 30 9月, 2011 1 次提交
  8. 28 9月, 2011 2 次提交
  9. 17 9月, 2011 1 次提交
    • T
      ipv6: Send ICMPv6 RSes only when RAs are accepted · 026359bc
      Tore Anderson 提交于
      This patch improves the logic determining when to send ICMPv6 Router
      Solicitations, so that they are 1) always sent when the kernel is
      accepting Router Advertisements, and 2) never sent when the kernel is
      not accepting RAs. In other words, the operational setting of the
      "accept_ra" sysctl is used.
      
      The change also makes the special "Hybrid Router" forwarding mode
      ("forwarding" sysctl set to 2) operate exactly the same as the standard
      Router mode (forwarding=1). The only difference between the two was
      that RSes was being sent in the Hybrid Router mode only. The sysctl
      documentation describing the special Hybrid Router mode has therefore
      been removed.
      
      Rationale for the change:
      
      Currently, the value of forwarding sysctl is the only thing determining
      whether or not to send RSes. If it has the value 0 or 2, they are sent,
      otherwise they are not. This leads to inconsistent behaviour in the
      following cases:
      
      * accept_ra=0, forwarding=0
      * accept_ra=0, forwarding=2
      * accept_ra=1, forwarding=2
      * accept_ra=2, forwarding=1
      
      In the first three cases, the kernel will send RSes, even though it will
      not accept any RAs received in reply. In the last case, it will not send
      any RSes, even though it will accept and process any RAs received. (Most
      routers will send unsolicited RAs periodically, so suppressing RSes in
      the last case will merely delay auto-configuration, not prevent it.)
      
      Also, it is my opinion that having the forwarding sysctl control RS
      sending behaviour (completely independent of whether RAs are being
      accepted or not) is simply not what most users would intuitively expect
      to be the case.
      Signed-off-by: NTore Anderson <tore@fud.no>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      026359bc
  10. 16 9月, 2011 2 次提交
  11. 08 9月, 2011 1 次提交
  12. 23 8月, 2011 1 次提交
  13. 19 8月, 2011 1 次提交
  14. 18 8月, 2011 1 次提交
  15. 14 8月, 2011 2 次提交
  16. 10 8月, 2011 1 次提交
  17. 08 8月, 2011 1 次提交
  18. 02 8月, 2011 1 次提交
  19. 22 7月, 2011 1 次提交
  20. 13 7月, 2011 1 次提交
  21. 09 7月, 2011 1 次提交
  22. 07 7月, 2011 1 次提交
    • S
      net: doc: fix compile warning of no format arguments in ifenslave.c · d804c6f2
      Shan Wei 提交于
      Fix following warning in ifenslave.c with gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu4).
      
      Documentation/networking/ifenslave.c:263:4: warning: format not a string literal and no format arguments
      Documentation/networking/ifenslave.c:271:3: warning: format not a string literal and no format arguments
      Documentation/networking/ifenslave.c:277:3: warning: format not a string literal and no format arguments
      Documentation/networking/ifenslave.c:285:3: warning: format not a string literal and no format arguments
      Documentation/networking/ifenslave.c:291:3: warning: format not a string literal and no format arguments
      Documentation/networking/ifenslave.c:292:3: warning: format not a string literal and no format arguments
      Documentation/networking/ifenslave.c:312:4: warning: format not a string literal and no format arguments
      Documentation/networking/ifenslave.c:323:3: warning: format not a string literal and no format arguments
      Documentation/networking/ifenslave.c:342:4: warning: format not a string literal and no format arguments
      Signed-off-by: NShan Wei <shanwei@cn.fujitsu.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      d804c6f2
  23. 06 7月, 2011 1 次提交
  24. 05 7月, 2011 2 次提交
  25. 09 6月, 2011 1 次提交
    • E
      inetpeer: remove unused list · 4b9d9be8
      Eric Dumazet 提交于
      Andi Kleen and Tim Chen reported huge contention on inetpeer
      unused_peers.lock, on memcached workload on a 40 core machine, with
      disabled route cache.
      
      It appears we constantly flip peers refcnt between 0 and 1 values, and
      we must insert/remove peers from unused_peers.list, holding a contended
      spinlock.
      
      Remove this list completely and perform a garbage collection on-the-fly,
      at lookup time, using the expired nodes we met during the tree
      traversal.
      
      This removes a lot of code, makes locking more standard, and obsoletes
      two sysctls (inet_peer_gc_mintime and inet_peer_gc_maxtime). This also
      removes two pointers in inet_peer structure.
      
      There is still a false sharing effect because refcnt is in first cache
      line of object [were the links and keys used by lookups are located], we
      might move it at the end of inet_peer structure to let this first cache
      line mostly read by cpus.
      Signed-off-by: NEric Dumazet <eric.dumazet@gmail.com>
      CC: Andi Kleen <andi@firstfloor.org>
      CC: Tim Chen <tim.c.chen@linux.intel.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      4b9d9be8
  26. 26 5月, 2011 1 次提交
  27. 20 5月, 2011 1 次提交
    • R
      Create Documentation/security/, · d410fa4e
      Randy Dunlap 提交于
      move LSM-, credentials-, and keys-related files from Documentation/
        to Documentation/security/,
      add Documentation/security/00-INDEX, and
      update all occurrences of Documentation/<moved_file>
        to Documentation/security/<moved_file>.
      d410fa4e
  28. 08 5月, 2011 1 次提交
  29. 30 4月, 2011 1 次提交
    • B
      ipv4, ipv6, bonding: Restore control over number of peer notifications · ad246c99
      Ben Hutchings 提交于
      For backward compatibility, we should retain the module parameters and
      sysfs attributes to control the number of peer notifications
      (gratuitous ARPs and unsolicited NAs) sent after bonding failover.
      Also, it is possible for failover to take place even though the new
      active slave does not have link up, and in that case the peer
      notification should be deferred until it does.
      
      Change ipv4 and ipv6 so they do not automatically send peer
      notifications on bonding failover.
      
      Change the bonding driver to send separate NETDEV_NOTIFY_PEERS
      notifications when the link is up, as many times as requested.  Since
      it does not directly control which protocols send notifications, make
      num_grat_arp and num_unsol_na aliases for a single parameter.  Bump
      the bonding version number and update its documentation.
      Signed-off-by: NBen Hutchings <bhutchings@solarflare.com>
      Signed-off-by: NJay Vosburgh <fubar@us.ibm.com>
      Acked-by: NBrian Haley <brian.haley@hp.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      ad246c99
  30. 14 4月, 2011 1 次提交
  31. 05 4月, 2011 1 次提交
  32. 31 3月, 2011 1 次提交
  33. 15 3月, 2011 1 次提交
  34. 10 3月, 2011 1 次提交
反馈
建议
客服 返回
顶部