All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jose Luis Domingo Lopez <linux-kernel@24x7linux.org>
To: linux-kernel@vger.kernel.org
Subject: Re: serious packet loss in 25Mbps load,frame size 64byte,duration 60 second. tested with smartbits
Date: Sun, 25 Aug 2002 14:03:05 +0200	[thread overview]
Message-ID: <20020825120305.GA7892@localhost> (raw)
In-Reply-To: <20020825104438.86663.qmail@web14508.mail.yahoo.com>

On Sunday, 25 August 2002, at 03:44:38 -0700,
Bergs wrote:

> My kernel is 2.4.16.
> performance of eepro100 driver 1.23b version.
> when the data load is 25% of
> 100Mbps,bi-directional,64byte frame size,and the test
> duration is 60 second,the test result display that
> serious packet loss take place. when the duration
> decrease to 10 second,the other test condition matain
> unchanged,no packet losss.
> 
The first should be to identify where the problem is. For example, run a
"vmstat 1" during the test to see if something looks unreasonable. At 25
Mbps bidirectional with a packet size of 64 bytes, there are nearly
50000 packets coming in and another 50000 going out. If there is an
interrupt for each packet sent/received (don't seem to be the case, at
least checking default module parameters for eepro100) you system will
have to deal with up to 100000 interrupts/second, quite a lot for a slow
system.

Hope it (somehow) helps :)

-- 
Jose Luis Domingo Lopez
Linux Registered User #189436     Debian Linux Woody (Linux 2.4.19-pre6aa1)

  reply	other threads:[~2002-08-25 11:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-25 10:44 serious packet loss in 25Mbps load,frame size 64byte,duration 60 second. tested with smartbits Bergs
2002-08-25 12:03 ` Jose Luis Domingo Lopez [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-26  2:16 Bergs
2002-08-26  2:17 Bergs

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=20020825120305.GA7892@localhost \
    --to=linux-kernel@24x7linux.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.