From: cliff white <cliffw@osdl.org>
To: Robert.Olsson@data.slu.se, netdev@oss.sgi.com
Subject: Constant errors with pktgen
Date: Mon, 14 Mar 2005 13:34:04 -0800 [thread overview]
Message-ID: <20050314133404.2528647f@es175> (raw)
Robert.
I am doing some wrapper scripts for pktgen for some testing purposes.
My test rig is two machines with an e100 card, connected by crossover cable.
When i run pktgen, the error counter == packet count, always.
Adding printk's, i see the error is coming from this bit past line 2688:
----------
now = getCurUs();
if (now > pkt_dev->next_tx_us) {
/* TODO: this code is slightly wonky. */
pkt_dev->errors++;
pkt_dev->next_tx_us = now - pkt_dev->delay_us;
pkt_dev->next_tx_ns = 0;
}
----------------
Any suggestions? More info if needed..
cliffw
--
"Ive always gone through periods where I bolt upright at four in the morning;
now at least theres a reason." -Michael Feldman
next reply other threads:[~2005-03-14 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 21:34 cliff white [this message]
2005-03-15 15:39 ` Constant errors with pktgen Robert Olsson
2005-03-15 19:04 ` cliff white
2005-03-16 22:50 ` David S. Miller
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=20050314133404.2528647f@es175 \
--to=cliffw@osdl.org \
--cc=Robert.Olsson@data.slu.se \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).