From: "Paul Rolland" <rol@as2917.net>
To: "'Corey Minyard'" <minyard@acm.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: e100 latency, cpu cycle saver and e1000...
Date: Wed, 21 May 2003 16:15:35 +0200 [thread overview]
Message-ID: <011a01c31fa3$725354e0$3f00a8c0@witbe> (raw)
In-Reply-To: <3ECB87F5.8060808@acm.org>
Hello,
> My little program was crude at best.
Yes, I know, but it does exist !
> You have to take into account what the machines are doing.
> If you notice, the "Min" latency is about the same, so it's
> not a CPU cycle saver. The long "Max" latencies mean you
> probably have something on IP2 that is blocking the execution
> of the IP stack (for, say up to 4.5ms).
> Are all the machine completely quiesced except for the test program?
> Have you tried switching the network connections to see if it
> is in the network hardware?
Correct, machines are not idle... but
- they are doing globally the same work,
- this behavior is something I can reproduce test after test, since
I've started this morning...
I started using that because IP1 was exhibiting high latency yesterday
'til I rebooted it, and since it is working quite fine...
Of course, I can reboot also IP2, but I'd like to understand why
and how to avoid it later...
Regards,
Paul
next prev parent reply other threads:[~2003-05-21 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-21 8:51 e100 latency, cpu cycle saver and e1000 Paul Rolland
2003-05-21 14:06 ` Corey Minyard
2003-05-21 14:15 ` Paul Rolland [this message]
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='011a01c31fa3$725354e0$3f00a8c0@witbe' \
--to=rol@as2917.net \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.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.