1. 16 10月, 2007 30 次提交
  2. 15 10月, 2007 4 次提交
  3. 14 10月, 2007 1 次提交
    • R
      net core: fix kernel-doc for new function parameters · c4ea43c5
      Randy Dunlap 提交于
      Fix networking code kernel-doc for newly added parameters.
      
      Warning(linux-2.6.23-git2//net/core/sock.c:879): No description found for parameter 'net'
      Warning(linux-2.6.23-git2//net/core/dev.c:570): No description found for parameter 'net'
      Warning(linux-2.6.23-git2//net/core/dev.c:594): No description found for parameter 'net'
      Warning(linux-2.6.23-git2//net/core/dev.c:617): No description found for parameter 'net'
      Warning(linux-2.6.23-git2//net/core/dev.c:641): No description found for parameter 'net'
      Warning(linux-2.6.23-git2//net/core/dev.c:667): No description found for parameter 'net'
      Warning(linux-2.6.23-git2//net/core/dev.c:722): No description found for parameter 'net'
      Warning(linux-2.6.23-git2//net/core/dev.c:959): No description found for parameter 'net'
      Warning(linux-2.6.23-git2//net/core/dev.c:1195): No description found for parameter 'dev'
      Warning(linux-2.6.23-git2//net/core/dev.c:2105): No description found for parameter 'n'
      Warning(linux-2.6.23-git2//net/core/dev.c:3272): No description found for parameter 'net'
      Warning(linux-2.6.23-git2//net/core/dev.c:3445): No description found for parameter 'net'
      Warning(linux-2.6.23-git2//include/linux/netdevice.h:1301): No description found for parameter 'cpu'
      Signed-off-by: NRandy Dunlap <randy.dunlap@oracle.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      c4ea43c5
  4. 13 10月, 2007 2 次提交
    • G
      kobjects: fix up improper use of the kobject name field · 19c38de8
      Greg Kroah-Hartman 提交于
      A number of different drivers incorrect access the kobject name field
      directly.  This is not correct as the name might not be in the array.
      Use the proper accessor function instead.
      19c38de8
    • K
      Driver core: change add_uevent_var to use a struct · 7eff2e7a
      Kay Sievers 提交于
      This changes the uevent buffer functions to use a struct instead of a
      long list of parameters. It does no longer require the caller to do the
      proper buffer termination and size accounting, which is currently wrong
      in some places. It fixes a known bug where parts of the uevent
      environment are overwritten because of wrong index calculations.
      
      Many thanks to Mathieu Desnoyers for finding bugs and improving the
      error handling.
      Signed-off-by: NKay Sievers <kay.sievers@vrfy.org>
      Cc: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
      Cc: Cornelia Huck <cornelia.huck@de.ibm.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      
      7eff2e7a
  5. 12 10月, 2007 3 次提交
    • I
      [TCP]: Limit processing lost_retrans loop to work-to-do cases · b08d6cb2
      Ilpo Järvinen 提交于
      This addition of lost_retrans_low to tcp_sock might be
      unnecessary, it's not clear how often lost_retrans worker is
      executed when there wasn't work to do.
      Signed-off-by: NIlpo Järvinen <ilpo.jarvinen@helsinki.fi>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      b08d6cb2
    • I
      [TCP]: Fix lost_retrans loop vs fastpath problems · f785a8e2
      Ilpo Järvinen 提交于
      Detection implemented with lost_retrans must work also when
      fastpath is taken, yet most of the queue is skipped including
      (very likely) those retransmitted skb's we're interested in.
      This problem appeared when the hints got added, which removed
      a need to always walk over the whole write queue head.
      Therefore decicion for the lost_retrans worker loop entry must
      be separated from the sacktag processing more than it was
      necessary before.
      
      It turns out to be problematic to optimize the worker loop
      very heavily because ack_seqs of skb may have a number of
      discontinuity points. Maybe similar approach as currently is
      implemented could be attempted but that's becoming more and
      more complex because the trend is towards less skb walking
      in sacktag marker. Trying a simple work until all rexmitted
      skbs heve been processed approach.
      
      Maybe after(highest_sack_end_seq, tp->high_seq) checking is not
      sufficiently accurate and causes entry too often in no-work-to-do
      cases. Since that's not known, I've separated solution to that
      from this patch.
      
      Noticed because of report against a related problem from TAKANO
      Ryousei <takano@axe-inc.co.jp>. He also provided a patch to
      that part of the problem. This patch includes solution to it
      (though this patch has to use somewhat different placement).
      TAKANO's description and patch is available here:
      
        http://marc.info/?l=linux-netdev&m=119149311913288&w=2
      
      ...In short, TAKANO's problem is that end_seq the loop is using
      not necessarily the largest SACK block's end_seq because the
      current ACK may still have higher SACK blocks which are later
      by the loop.
      Signed-off-by: NIlpo Järvinen <ilpo.jarvinen@helsinki.fi>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      f785a8e2
    • I
      [TCP]: No need to re-count fackets_out/sacked_out at RTO · 4cd82999
      Ilpo Järvinen 提交于
      Both sacked_out and fackets_out are directly known from how
      parameter. Since fackets_out is accurate, there's no need for
      recounting (sacked_out was previously unnecessarily counted
      in the loop anyway).
      Signed-off-by: NIlpo Järvinen <ilpo.jarvinen@helsinki.fi>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      4cd82999