netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Radensky <felix@allot.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	"Feldman, Scott" <scott.feldman@intel.com>,
	netdev@oss.sgi.com
Subject: Re: e100 "Ferguson" release
Date: Tue, 05 Aug 2003 11:23:22 +0300	[thread overview]
Message-ID: <3F2F697A.2020708@allot.com> (raw)
In-Reply-To: 3F2CBA71.2070503@candelatech.com

I've also noticed that the number of hard_start_xmit failures in e1000
has increased significantly in version 5.1.13-k1. In version 5.0.43-k1 the
number of failures was much smaller.

Felix.

Ben Greear wrote:

>
>
>
> With e100 and e1000, I see the very large numbers of the 
> hard_start_xmit failure
> when running very high packets-per-second rates (small packets).
> I see virtually no failures with tulip.  pktgen knows how to re-queue, 
> but it's
> curious it has to so often.  For code that does not requeue, this 
> could be even
> more of a bummer.
>
>
>

  parent reply	other threads:[~2003-08-05  8:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-03  4:34 e100 "Ferguson" release Feldman, Scott
2003-08-03  6:06 ` Jeff Garzik
2003-08-03  6:12   ` Jeff Garzik
2003-08-03  7:32   ` Ben Greear
2003-08-03  7:32     ` David S. Miller
2003-08-04  3:09       ` David Brownell
2003-08-04  3:08         ` David S. Miller
2003-08-04  3:45           ` David Brownell
2003-08-04  3:46             ` David S. Miller
2003-08-04  4:08               ` David Brownell
2003-08-04  4:13                 ` David S. Miller
2003-08-04 17:38                   ` David Brownell
2003-08-05  8:23     ` Felix Radensky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-05  3:45 Feldman, Scott
2003-08-05  5:29 ` Jeff Garzik
2003-08-05  7:16 ` David S. Miller
2003-08-05 14:28 Feldman, Scott
2003-08-05 15:19 Feldman, Scott
2003-08-05 15:24 ` Jeff Garzik
2003-08-10  9:00   ` Felix Radensky
2003-08-05 15:44 ` Felix Radensky

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=3F2F697A.2020708@allot.com \
    --to=felix@allot.com \
    --cc=greearb@candelatech.com \
    --cc=jgarzik@pobox.com \
    --cc=netdev@oss.sgi.com \
    --cc=scott.feldman@intel.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).