From: cliff white <cliffw@osdl.org>
To: Robert Olsson <Robert.Olsson@data.slu.se>, netdev@oss.sgi.com
Subject: Re: Constant errors with pktgen
Date: Tue, 15 Mar 2005 11:04:14 -0800 [thread overview]
Message-ID: <20050315110414.3310bf96@es175> (raw)
In-Reply-To: <16951.422.818446.117190@robur.slu.se>
On Tue, 15 Mar 2005 16:39:18 +0100
Robert Olsson <Robert.Olsson@data.slu.se> wrote:
>
> cliff white writes:
>
> > My test rig is two machines with an e100 card, connected by crossover
> > cable.
> >
> > When i run pktgen, the error counter == packet count, always.
>
> I see. Try the patch patch below it cleans up the code a bit and
> restores the old meaning of error. It also has the minor fix from
> Adrian Bunk
>
Works for me
Current:
pkts-sofar: 7400227 errors: 0
( now i have to force some errors... )
cliffw
> --ro
>
> --- net/core/pktgen.c.050315 2005-03-11 10:48:43.000000000 +0100
> +++ net/core/pktgen.c 2005-03-15 16:16:01.000000000 +0100
> @@ -151,7 +151,7 @@
> #include <asm/timex.h>
>
>
> -#define VERSION "pktgen v2.60: Packet Generator for packet performance testing.\n"
> +#define VERSION "pktgen v2.61: Packet Generator for packet performance testing.\n"
>
> /* #define PG_DEBUG(a) a */
> #define PG_DEBUG(a)
> @@ -2590,7 +2590,7 @@
> thread_unlock();
> }
>
> -__inline__ void pktgen_xmit(struct pktgen_dev *pkt_dev)
> +static __inline__ void pktgen_xmit(struct pktgen_dev *pkt_dev)
> {
> struct net_device *odev = NULL;
> __u64 idle_start = 0;
> @@ -2654,7 +2654,6 @@
>
> spin_lock_bh(&odev->xmit_lock);
> if (!netif_queue_stopped(odev)) {
> - u64 now;
>
> atomic_inc(&(pkt_dev->skb->users));
> retry_now:
> @@ -2678,24 +2677,18 @@
>
> pkt_dev->errors++;
> pkt_dev->last_ok = 0;
> - pkt_dev->next_tx_us = getCurUs(); /* TODO */
> - pkt_dev->next_tx_ns = 0;
> }
>
> + pkt_dev->next_tx_us = getCurUs();
> + pkt_dev->next_tx_ns = 0;
> +
> pkt_dev->next_tx_us += pkt_dev->delay_us;
> pkt_dev->next_tx_ns += pkt_dev->delay_ns;
> +
> if (pkt_dev->next_tx_ns > 1000) {
> pkt_dev->next_tx_us++;
> pkt_dev->next_tx_ns -= 1000;
> }
> -
> - 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;
> - }
> }
>
> else { /* Retry it next time */
>
--
"Ive always gone through periods where I bolt upright at four in the morning;
now at least theres a reason." -Michael Feldman
next prev parent reply other threads:[~2005-03-15 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 21:34 Constant errors with pktgen cliff white
2005-03-15 15:39 ` Robert Olsson
2005-03-15 19:04 ` cliff white [this message]
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=20050315110414.3310bf96@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).