From: "gis88530" <gis88530@cis.nctu.edu.tw>
To: <linux-kernel@vger.kernel.org>
Subject: kernel benchmark
Date: Fri, 16 Mar 2001 10:52:27 +0800 [thread overview]
Message-ID: <000b01c0adc4$2482c8c0$ae58718c@cis.nctu.edu.tw> (raw)
In-Reply-To: <Pine.LNX.4.33.0103152222121.1320-100000@duckman.distro.conectiva>
Hi,
I use kernprof+gprof to measure the 2.2.16 kernel,
but the scale is mini-second.
So I use do_gettimeofday( ) kernel function call to measure
the latency. (This function support micro-second scale.)
Moreover, I use SmartBits packet generator to generate
the specific network traffic load. The environment is
as follows. However, the result are very funny. I think
that latency should increase progressively when load
increase, but the result are unable explaining.
Could you give me some hint? Thanks a lot.
1518byte packet
load latency(us)
1% 13.1284
10% 14.1629
20% 12.6558
30% 11.1056
40% 10.7510
50% 10.4148
60% 10.3337
70% 10.1038
80% 10.1103
90% 10.3634
100% 11.2367
64byte packet
load latency(us)
1% 3.6767
10% 2.7696
20% 4.3926
30% 2.8135
40% 8.2552
50% 5.3088
60% 9.3744
70% 23.6247
80% 8.5351
90% 9.7217
100% 13.065
Benchmark Environment:
+---smartbits<---+
| |
+---->Linux-----+
* The do_gettimeofday function call is as follows:
--------------
do_gettimeofday(&begin);
...
(kernel do something)
...
do_gettimeofday(&end);
if (end.tv_usec < begin.tv_usec) {
end.tv_usec += 1000000; end.tv_sec--;
}
end.tv_sedc -= begin.tv_sec;
end.tv_usec -= begin.tv_usec;
return ((end.tv_sec*1000000) + end.tv_usec);
next prev parent reply other threads:[~2001-03-16 2:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-15 12:28 Is swap == 2 * RAM a permanent thing? Mike A. Harris
2001-03-15 13:08 ` Rik van Riel
2001-03-15 14:24 ` Mike Harrold
2001-03-16 0:47 ` Rik van Riel
2001-03-15 16:09 ` christophe barbe
2001-03-15 23:26 ` Rik van Riel
2001-03-15 17:20 ` christophe barbe
2001-03-15 17:43 ` James Lewis Nance
2001-03-16 1:25 ` Rik van Riel
2001-03-16 2:52 ` gis88530 [this message]
2001-03-15 15:23 ` Ketil Froyn
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='000b01c0adc4$2482c8c0$ae58718c@cis.nctu.edu.tw' \
--to=gis88530@cis.nctu.edu.tw \
--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
all inboxes | Powered by JetHome®