netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: netdev@vger.kernel.org
Subject: Re: forcedeth driver hangs under heavy load
Date: Tue, 13 Apr 2010 19:22:32 +0200	[thread overview]
Message-ID: <4BC4A858.9010009@gmail.com> (raw)

stephen mulcahy  wrote:

> running Hadoop[1] TeraSort[2] but I haven't identified a simpler 
> reproducer. I tried to recreate this with iperf and ping -f but neither 
> helped - it may be that the problem only occurs when systems are passing 
> large amounts of traffic and have very high cpu utilisation (when 

Did you try ISIC(IP Stack Integrity Checker)[1] tools ?

Net-drivers usually break running these tools.


[1] http://isic.sf.net needs libnet[2]
[2] http://github.com/sam-github/libnet

-- 
«Allá muevan feroz guerra, ciegos reyes por un palmo más de tierra;
que yo aquí tengo por mío cuanto abarca el mar bravío, a quien nadie
impuso leyes. Y no hay playa, sea cualquiera, ni bandera de esplendor,
que no sienta mi derecho y dé pecho a mi valor.»

             reply	other threads:[~2010-04-13 17:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-13 17:22 Xose Vazquez Perez [this message]
     [not found] <4B9E6C60.7030300@atlanticlinux.ie>
     [not found] ` <20100315182220.GQ2763@decadent.org.uk>
     [not found]   ` <4B9F5E5E.2060209@atlanticlinux.ie>
     [not found]     ` <1270393967.8341.11.camel@localhost>
     [not found]       ` <4BBCA19C.5080204@atlanticlinux.ie>
2010-04-10 23:36         ` forcedeth driver hangs under heavy load Ben Hutchings
2010-04-12 10:01           ` Bug#572201: " stephen mulcahy
2010-04-12 12:39             ` stephen mulcahy
2010-04-12 12:47               ` Eric Dumazet
2010-04-12 13:05                 ` stephen mulcahy
2010-04-12 13:19                   ` stephen mulcahy
2010-04-12 15:24                     ` Eric Dumazet
2010-04-12 16:11                       ` stephen mulcahy
2010-04-12 16:59                         ` Eric Dumazet
2010-04-13 10:03                           ` stephen mulcahy
2010-04-13 10:49                             ` Eric Dumazet
2010-04-13 11:00                               ` stephen mulcahy
2010-04-13 12:04                                 ` Ben Hutchings
2010-04-13 14:27                                   ` stephen mulcahy
2010-04-13 14:42                                     ` Eric Dumazet
2010-04-13 14:49                                       ` stephen mulcahy
2010-04-13 15:00                                         ` stephen mulcahy
2010-04-13 15:05                                         ` Eric Dumazet
2010-04-13 15:08                                           ` stephen mulcahy
2010-04-13 15:22                                             ` Eric Dumazet
2010-04-13 15:25                                               ` stephen mulcahy
2010-04-13 20:01                                                 ` Eric Dumazet
2010-04-13 21:43                                       ` David Miller
2010-04-13 21:46                                         ` Eric Dumazet
2010-04-14  5:33                                           ` Bug#572201: " Ayaz Abdulla
2010-04-14  1:41                                             ` David Miller
2010-04-14 14:30                                             ` stephen mulcahy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BC4A858.9010009@gmail.com \
    --to=xose.vazquez@gmail.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).