From: "Jeff V. Merkey" <jmerkey@devicelogics.com>
To: linux-kernel@vger.kernel.org, jmerkey@drdos.com
Subject: Linux 2.6.9 pktgen module causes INIT process respawning and sickness
Date: Fri, 19 Nov 2004 14:53:08 -0700 [thread overview]
Message-ID: <419E6B44.8050505@devicelogics.com> (raw)
With pktgen.o configured to send 123MB/S on a gigabit on a system using
pktgen set to the following parms:
pgset "odev eth1"
pgset "pkt_size 1500"
pgset "count 0"
pgset "ipg 5000"
pgset "src_min 10.0.0.1"
pgset "src_max 10.0.0.254"
pgset "dst_min 192.168.0.1"
pgset "dst_max 192.168.0.254"
After 37 hours of continual packet generation into a gigabit
regeneration tap device,
the server system console will start to respawn the INIT process about
every 10-12
hours of continuous packet generation.
As a side note, this module in Linux is extremely useful and the "USE
WITH CAUTION" warnings
are certainly will stated. The performance of this tool is excellent.
Jeff
next reply other threads:[~2004-11-19 21:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 21:53 Jeff V. Merkey [this message]
2004-11-19 22:06 ` Linux 2.6.9 pktgen module causes INIT process respawning and sickness Jeff V. Merkey
2004-11-22 3:44 ` Lincoln Dale
2004-11-22 17:06 ` Jeff V. Merkey
2004-11-22 22:50 ` Lincoln Dale
2004-11-23 0:36 ` Jeff V. Merkey
2004-11-23 1:06 ` Jeff V. Merkey
2004-11-23 1:25 ` Lincoln Dale
2004-11-23 1:23 ` Lincoln Dale
2004-11-22 17:19 ` Martin Josefsson
2004-11-22 18:33 ` Jeff V. Merkey
-- strict thread matches above, loose matches on Subject: below --
2004-11-22 18:30 Jeff V. Merkey
[not found] <419E6B44.8050505@devicelogics.com.suse.lists.linux.kernel>
[not found] ` <5.1.0.14.2.20041122144144.04e3d9f0@171.71.163.14.suse.lists.linux.kernel>
[not found] ` <5.1.0.14.2.20041123094109.04003720@171.71.163.14.suse.lists.linux.kernel>
[not found] ` <41A2862A.2000602@devicelogics.com.suse.lists.linux.kernel>
2004-11-23 20:40 ` Andi Kleen
2004-11-23 21:57 ` Jeff V. Merkey
2004-11-23 22:27 ` Andi Kleen
2004-11-23 22:54 ` Jeff V. Merkey
2004-11-25 2:17 ` Lincoln Dale
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=419E6B44.8050505@devicelogics.com \
--to=jmerkey@devicelogics.com \
--cc=jmerkey@drdos.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 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.