netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: claudiu.manoil@freescale.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] gianfar: Tx timeout issue
Date: Mon, 10 Mar 2014 13:18:27 -0400 (EDT)	[thread overview]
Message-ID: <20140310.131827.672807362272151307.davem@davemloft.net> (raw)
In-Reply-To: <1394196166-24932-1-git-send-email-claudiu.manoil@freescale.com>

From: Claudiu Manoil <claudiu.manoil@freescale.com>
Date: Fri, 7 Mar 2014 14:42:44 +0200

> There's an older Tx timeout issue showing up on etsec2 devices
> with 2 CPUs.  I pinned this issue down to processing overhead
> incurred by supporting multiple Tx/Rx rings, as explained in
> the 2nd patch below.  But before this, there's also a concurency
> issue leading to Rx/Tx spurrious interrupts, addressed by the
> 'Tx NAPI' patch below.
> The Tx timeout can be triggered with multiple Tx flows,
> 'iperf -c -N 8' commands, on a 2 CPUs etsec2 based (P1020) board.

Series applied, thanks.

  parent reply	other threads:[~2014-03-10 17:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07 12:42 [PATCH net-next v2 0/2] gianfar: Tx timeout issue Claudiu Manoil
2014-03-07 12:42 ` [PATCH net-next v2 1/2] gianfar: Separate out the Tx interrupt handling (Tx NAPI) Claudiu Manoil
2014-03-07 12:42 ` [PATCH net-next v2 2/2] gianfar: Use Single-Queue polling for "fsl,etsec2" Claudiu Manoil
2014-03-07 14:50   ` Claudiu Manoil
2014-03-10 17:18 ` David Miller [this message]
2014-03-11  8:10   ` [PATCH net-next v2 0/2] gianfar: Tx timeout issue Claudiu Manoil

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=20140310.131827.672807362272151307.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=claudiu.manoil@freescale.com \
    --cc=netdev@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 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).