1. 30 11月, 2006 3 次提交
  2. 04 10月, 2006 10 次提交
  3. 29 9月, 2006 1 次提交
  4. 26 9月, 2006 1 次提交
    • J
      [PATCH] bonding: Validate probe replies in ARP monitor · f5b2b966
      Jay Vosburgh 提交于
      	Add logic to check ARP request / reply packets used for ARP
      monitor link integrity checking.
      
      	The current method simply examines the slave device to see if it
      has sent and received traffic; this can be fooled by extraneous traffic.
      For example, if multiple hosts running bonding are behind a common
      switch, the probe traffic from the multiple instances of bonding will
      update the tx/rx times on each other's slave devices.
      Signed-off-by: NJay Vosburgh <fubar@us.ibm.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      f5b2b966
  5. 25 9月, 2006 1 次提交
  6. 23 9月, 2006 3 次提交
  7. 18 9月, 2006 1 次提交
  8. 18 8月, 2006 1 次提交
  9. 29 7月, 2006 1 次提交
    • R
      [PATCH] qla3xxx NIC driver · 5a4faa87
      Ron Mercer 提交于
      This is a complementary network driver for our ISP4XXX parts.
      
      There is a concurrent effort underway to get the iSCSI driver (qla4xxx)
      integrated upstream as well.
      
      I have been through several iterations with the linux-netdev list and have had
      much response from Stephen Hemminger.
      
      - Built and tested using kernel 2.6.17-rc4.
      
      - The chip supports two ethernet and two iSCSI functions.
      
      - The functions ql_sem_lock, ql_sem_spinlock, ql_sem_unlock, and
        ql_wait_for_drvr_lock are used to protect resources that are shared across
        the network and iSCSI functions.  This protection is mostly during chip
        initialization and resets, but also include link management.
      
      - The PHY/MII are not exported through ethtool due to the fact that the
        iSCSI function will control the common link at least 50% of the time.
      
      This driver has been through several iterations on the netdev list and we feel
      this driver is ready for inclusion in the upstream kernel.
      
      It has been built and tested on x86 and PPC64 platforms.
      
      Cc: Jeff Garzik <jeff@garzik.org>
      Cc: Stephen Hemminger <shemminger@osdl.org>
      Signed-off-by: NRon Mercer <ron.mercer@qlogic.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      5a4faa87
  10. 04 7月, 2006 1 次提交
  11. 01 7月, 2006 1 次提交
  12. 23 6月, 2006 1 次提交
  13. 18 6月, 2006 2 次提交
    • D
      [TCP]: Add tcp_slow_start_after_idle sysctl. · 35089bb2
      David S. Miller 提交于
      A lot of people have asked for a way to disable tcp_cwnd_restart(),
      and it seems reasonable to add a sysctl to do that.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      35089bb2
    • H
      [NET]: Add netif_tx_lock · 932ff279
      Herbert Xu 提交于
      Various drivers use xmit_lock internally to synchronise with their
      transmission routines.  They do so without setting xmit_lock_owner.
      This is fine as long as netpoll is not in use.
      
      With netpoll it is possible for deadlocks to occur if xmit_lock_owner
      isn't set.  This is because if a printk occurs while xmit_lock is held
      and xmit_lock_owner is not set can cause netpoll to attempt to take
      xmit_lock recursively.
      
      While it is possible to resolve this by getting netpoll to use
      trylock, it is suboptimal because netpoll's sole objective is to
      maximise the chance of getting the printk out on the wire.  So
      delaying or dropping the message is to be avoided as much as possible.
      
      So the only alternative is to always set xmit_lock_owner.  The
      following patch does this by introducing the netif_tx_lock family of
      functions that take care of setting/unsetting xmit_lock_owner.
      
      I renamed xmit_lock to _xmit_lock to indicate that it should not be
      used directly.  I didn't provide irq versions of the netif_tx_lock
      functions since xmit_lock is meant to be a BH-disabling lock.
      
      This is pretty much a straight text substitution except for a small
      bug fix in winbond.  It currently uses
      netif_stop_queue/spin_unlock_wait to stop transmission.  This is
      unsafe as an IRQ can potentially wake up the queue.  So it is safer to
      use netif_tx_disable.
      
      The hamradio bits used spin_lock_irq but it is unnecessary as
      xmit_lock must never be taken in an IRQ handler.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      932ff279
  14. 09 6月, 2006 1 次提交
  15. 10 5月, 2006 1 次提交
  16. 25 4月, 2006 2 次提交
  17. 15 4月, 2006 1 次提交
  18. 01 4月, 2006 2 次提交
  19. 29 3月, 2006 2 次提交
  20. 28 3月, 2006 2 次提交
  21. 27 3月, 2006 1 次提交
  22. 26 3月, 2006 1 次提交