All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul Rolland" <rol@as2917.net>
To: <linux-kernel@vger.kernel.org>
Cc: <rol@as2917.net>
Subject: e100 latency, cpu cycle saver and e1000...
Date: Wed, 21 May 2003 10:51:21 +0200	[thread overview]
Message-ID: <00e701c31f76$26fea350$3f00a8c0@witbe> (raw)

Hello,

A few days ago, there was a thread about e100 latency related to
CPU Cycle Saver...

Suggestion was to disabled it to return back to some "standard"
latency.

At the moment, I'm experiencing some strange behavior, not with
an e100 but with an e1000 on a 2.4.20 kernel...

Here are some traces, using Corey Minyard test application :

[root@IP3 tmp]# ./test IP1 32000 10000 370
Average: 201us, Max: 631us, Min: 200us
[root@IP3 tmp]# ./test IP2 32000 10000 370
Average: 422us, Max: 47581us, Min: 209us

All three machines are using 2.4.20 and e1000 drivers, they are
the same hardware.

But, definitely, IP2 is exhibiting much higher max latency...

Increasing the packet size up to 1200 bytes doesn't change the 
global behavior : IP2 is always much "latent" than IP1...

The problem is that it seems there is no CPU Cycle Saver on e1000
NIC. Is there some equivalent ? Could someone give a guess on
what's going on ?

Regards,
Paul


             reply	other threads:[~2003-05-21  8:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-21  8:51 Paul Rolland [this message]
2003-05-21 14:06 ` e100 latency, cpu cycle saver and e1000 Corey Minyard
2003-05-21 14:15   ` Paul Rolland
2003-05-21 22:50     ` Zwane Mwaikambo
2003-05-22  5:49       ` Paul Rolland
2003-05-22  5:46         ` Zwane Mwaikambo

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='00e701c31f76$26fea350$3f00a8c0@witbe' \
    --to=rol@as2917.net \
    --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.