1. 03 12月, 2006 3 次提交
    • S
      netpoll retry cleanup · 2bdfe0ba
      Stephen Hemminger 提交于
      The netpoll beast was still not happy. If the beast got
      clogged pipes, it tended to stare blankly off in space
      for a long time.
      
      The problem couldn't be completely fixed because the
      beast talked with irq's disabled. But it could be made
      less painful and shorter.
      Signed-off-by: NStephen Hemminger <shemminger@osdl.org>
      2bdfe0ba
    • S
      netpoll per device txq · b6cd27ed
      Stephen Hemminger 提交于
      When the netpoll beast got really busy, it tended to clog
      things, so it stored them for later. But the beast was putting
      all it's skb's in one basket. This was bad because maybe some
      pipes were clogged and others were not.
      Signed-off-by: NStephen Hemminger <shemminger@osdl.org>
      b6cd27ed
    • S
      netpoll info leak · 93ec2c72
      Stephen Hemminger 提交于
      After looking harder, Steve noticed that the netpoll
      beast leaked a little every time it shutdown for a nap.
      Not a big leak, but a nuisance kind of thing.
      
      He took out his refcount duct tape and patched the
      leak. It was overkill since there was already other
      locking in that area, but it looked clean and wouldn't
      attract fleas.
      Signed-off-by: NStephen Hemminger <shemminger@osdl.org>
      93ec2c72
  2. 26 6月, 2006 1 次提交
  3. 13 10月, 2005 1 次提交
  4. 12 8月, 2005 2 次提交
  5. 23 6月, 2005 3 次提交
    • J
      [NETPOLL]: allow multiple netpoll_clients to register against one interface · fbeec2e1
      Jeff Moyer 提交于
      This patch provides support for registering multiple netpoll clients to the
      same network device.  Only one of these clients may register an rx_hook,
      however.  In practice, this restriction has not been problematic.  It is
      worth mentioning, though, that the current design can be easily extended to
      allow for the registration of multiple rx_hooks.
      
      The basic idea of the patch is that the rx_np pointer in the netpoll_info
      structure points to the struct netpoll that has rx_hook filled in.  Aside
      from this one case, there is no need for a pointer from the struct
      net_device to an individual struct netpoll.
      
      A lock is introduced to protect the setting and clearing of the np_rx
      pointer.  The pointer will only be cleared upon netpoll client module
      removal, and the lock should be uncontested.
      Signed-off-by: NJeff Moyer <jmoyer@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      fbeec2e1
    • J
      [NETPOLL]: Introduce a netpoll_info struct · 115c1d6e
      Jeff Moyer 提交于
      This patch introduces a netpoll_info structure, which the struct net_device
      will now point to instead of pointing to a struct netpoll.  The reason for
      this is two-fold: 1) fields such as the rx_flags, poll_owner, and poll_lock
      should be maintained per net_device, not per netpoll;  and 2) this is a first
      step in providing support for multiple netpoll clients to register against the
      same net_device.
      
      The struct netpoll is now pointed to by the netpoll_info structure.  As
      such, the previous behaviour of the code is preserved.
      Signed-off-by: NJeff Moyer <jmoyer@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      115c1d6e
    • J
      [NETPOLL]: Set poll_owner to -1 before unlocking in netpoll_poll_unlock() · 6ca4f65e
      Jeff Moyer 提交于
      This trivial patch moves the assignment of poll_owner to -1 inside of
      the lock.  This fixes a potential SMP race in the code.
      Signed-off-by: NJeff Moyer <jmoyer@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6ca4f65e
  6. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4