netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Acker <dacker@roinet.com>
To: James Chapman <jchapman@katalix.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	"Kok, Auke" <auke-jan.h.kok@intel.com>,
	John Ronciak <john.ronciak@intel.com>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
	Milton Miller <miltonm@bga.com>,
	netdev@vger.kernel.org, e1000-devel@lists.sourceforge.net,
	Scott Feldman <sfeldma@pobox.com>
Subject: Re: [PATCH] Fix e100 on systems that have cache incoherent DMA
Date: Wed, 12 Sep 2007 16:11:21 -0400	[thread overview]
Message-ID: <46E847E9.4010601@roinet.com> (raw)
In-Reply-To: <46E7CDD5.3060306@katalix.com>

James Chapman wrote:
> David Acker wrote:
>> Jeff Garzik wrote:
>>> pktgen outputs for the various cases modified/unmodified[/others?] 
>>> would be nice, if you have a spot of time.
>>>
>>>     Jeff
>>
>> I am not familiar with pktgen but I seem to have it working for a 
>> simple test.
>> I edited the 1-1 example from 
>> ftp://robur.slu.se/pub/Linux/net-development/pktgen-testing/examples/ 
>> .  The results with and without the patch are below. 
> 
> It looks like you ran pktgen on the embedded system, which exercised 
> only the transmit path. Auke indicated that the lockup was in the RU. 
> Have you run pktgen on a test system to fire packets at the embedded 
> system at max rate? Also test what happens when you fire packets in both 
> directions simultaneously.
> 
It appears that running pktgen between my pc and the embedded device at the same time eventually hangs the RU.  I will 
be looking into this failure in detail and report back when I know more.  Thanks for bearing with me on this!
-Ack

  reply	other threads:[~2007-09-12 20:11 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31 20:54 [PATCH] Fix e100 on systems that have cache incoherent DMA David Acker
2007-09-04 17:02 ` Kok, Auke
2007-09-07 16:31 ` Kok, Auke
2007-09-07 20:41   ` David Acker
2007-09-07 21:03     ` Kok, Auke
2007-09-07 21:18       ` Kok, Auke
2007-09-07 23:24     ` Jeff Garzik
2007-09-11 20:54       ` David Acker
2007-09-12 11:30         ` James Chapman
2007-09-12 20:11           ` David Acker [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-11-02 13:27 David Acker
2007-11-02 16:05 ` Kok, Auke
2007-11-02 16:11   ` Jeff Garzik
2007-11-06 17:01 ` Kok, Auke
2007-11-08 18:17 Auke Kok
2007-11-28 19:12 ` David Acker
2007-11-28 19:21   ` Kok, Auke
2007-11-28 19:26     ` Jeff Garzik
2007-11-28 19:50       ` David Acker
2008-06-18 18:54         ` Anders Grafström
2008-06-18 19:16           ` David Acker
2008-06-19 12:38             ` Anders Grafström
2008-07-01  8:26               ` Andrew Morton
2008-07-01  9:49                 ` Jeff Garzik
2008-07-01 18:07                   ` Andrew Morton
2008-07-02 17:36                     ` Anders Grafström
2008-07-02 17:45                       ` Andrew Morton
2008-07-01 21:35           ` David Acker

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=46E847E9.4010601@roinet.com \
    --to=dacker@roinet.com \
    --cc=auke-jan.h.kok@intel.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=jchapman@katalix.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=jgarzik@pobox.com \
    --cc=john.ronciak@intel.com \
    --cc=miltonm@bga.com \
    --cc=netdev@vger.kernel.org \
    --cc=sfeldma@pobox.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).