public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [BETA] First test release of Tigon3 driver
Date: Wed, 27 Feb 2002 11:30:57 -0500	[thread overview]
Message-ID: <3C7D09C1.62BFB539@nortelnetworks.com> (raw)
In-Reply-To: <20020227125611.A20415@stud.ntnu.no> <20020227.040653.58455636.davem@redhat.com> <20020227132454.B24996@stud.ntnu.no> <20020227.042845.54186884.davem@redhat.com> <20020227170321.B22422@stud.ntnu.no>

Thomas Langås wrote:
> 
> David S. Miller:
> > At this point I'm mostly interested in if it works at all :-)
> > If the answer is yes, tell me that and then you can feel
> > free to experiment with jumbo frames et al. to discover
> > other bugs in the driver :-)
> 
> Just tested with MTU set at 1500 for now, but it seems to work fine, did a
> netcat between two boxes on the same switch and got around 80MB/sec.
> 
> Any programs or anything that could do a serious stresstest?  (Both hosts
> are Dell PowerEdge 2550, RedHat Linux 7.2).

I've had good luck with an infinite loop on sendto().  Can easily saturate a
link, and depending on the receiving host, can essentially DOS the machine.

As an example, a Dell OptiPlex GX1 running 2.4.17 becomes completely unusable
when receiving 80000 packets/sec.

Chris

-- 
Chris Friesen                    | MailStop: 043/33/F10  
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com

  parent reply	other threads:[~2002-02-27 16:23 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-26  0:59 [BETA] First test release of Tigon3 driver David S. Miller
2002-02-26  3:43 ` nick
2002-02-26  4:40   ` David S. Miller
2002-02-26 11:22     ` Sebastian Heidl
2002-02-26 11:24       ` David S. Miller
2002-02-26 11:39         ` Sebastian Heidl
2002-02-26 13:13           ` David S. Miller
2002-02-26 13:57 ` Thomas Langås
2002-02-26 14:59   ` David S. Miller
2002-02-26 15:40     ` Thomas Langås
2002-02-26 16:09       ` __skb_dequeue irq race ? Bjorn Wesen
2002-02-27  2:56       ` [BETA] First test release of Tigon3 driver David S. Miller
     [not found]         ` <20020227102450.B23121@stud.ntnu.no>
2002-02-27  9:31           ` David S. Miller
2002-02-27 11:05         ` Thomas Langås
2002-02-27 11:34           ` David S. Miller
2002-02-27 11:56             ` Thomas Langås
2002-02-27 12:06               ` David S. Miller
2002-02-27 12:24                 ` Thomas Langås
2002-02-27 12:28                   ` David S. Miller
2002-02-27 16:03                     ` Thomas Langås
2002-02-27 16:10                       ` Arjan van de Ven
2002-02-27 17:25                         ` Thomas Langås
2002-02-27 18:37                         ` Zach Brown
2002-02-27 18:46                           ` Zach Brown
2002-02-27 19:42                         ` Thomas Langås
2002-02-27 16:30                       ` Chris Friesen [this message]
2002-02-26 17:22 ` Greg KH
2002-02-27  4:13   ` David S. Miller
2002-02-26 18:08 ` Pasi Kärkkäinen
2002-02-27  2:12   ` David S. Miller
  -- strict thread matches above, loose matches on Subject: below --
2002-03-12  0:57 Timothy Ngo
2002-03-12  1:21 ` Alan Cox
2002-03-12  6:47 ` David S. Miller

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=3C7D09C1.62BFB539@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=linux-kernel@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