From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Keitel, Tino (ALC NetworX GmbH)" <Tino.Keitel@alcnetworx.de>
Cc: Tino Keitel <tino.keitel@tikei.de>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: BQL support in gianfar causes network hickup
Date: Tue, 27 Nov 2012 05:32:42 -0800 [thread overview]
Message-ID: <1354023162.7553.1708.camel@edumazet-glaptop> (raw)
In-Reply-To: <9AA65D849A88EB44B5D9B6A8BA098E23040A60D6EE71@Exchange1.lawo.de>
On Tue, 2012-11-27 at 13:42 +0100, Keitel, Tino (ALC NetworX GmbH)
wrote:
> On Di, 2012-11-27 at 04:36 -0800, Eric Dumazet wrote:
> >
> > Can you reproduce the problem using a single cpu ?
>
> Yes, it is a single-CPU system.
Can you reproduce the problem without PTP running, or disabled in the
driver ?
(comment the "priv->hwts_tx_en = 1;" line)
This looks like we miss an interrupt ( or TXBD_INTERRUPT not correctly
set)
And it could be a bug occurring if we try to send one skb with fragments
and skb_shinfo(skb)->tx_flags & SKBTX_HW_TSTAMP
next prev parent reply other threads:[~2012-11-27 13:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 15:58 BQL support in gianfar causes network hickup Keitel, Tino (ALC NetworX GmbH)
2012-11-23 16:34 ` Paul Gortmaker
2012-11-23 19:42 ` Francois Romieu
2012-11-24 20:42 ` Tino Keitel
2012-11-24 23:43 ` Eric Dumazet
2012-11-26 10:01 ` Tino Keitel
2012-11-26 16:34 ` Eric Dumazet
2012-11-26 17:08 ` Keitel, Tino (ALC NetworX GmbH)
2012-11-26 17:17 ` Eric Dumazet
2012-11-27 9:36 ` Keitel, Tino (ALC NetworX GmbH)
2012-11-27 12:36 ` Eric Dumazet
2012-11-27 12:42 ` Keitel, Tino (ALC NetworX GmbH)
2012-11-27 13:32 ` Eric Dumazet [this message]
2012-11-27 13:49 ` Eric Dumazet
2013-02-05 13:00 ` Keitel, Tino (ALC NetworX GmbH)
2013-02-06 1:55 ` Paul Gortmaker
2013-02-06 15:20 ` Keitel, Tino (ALC NetworX GmbH)
2013-04-29 13:14 ` Claudiu Manoil
2013-04-29 13:20 ` Tino Keitel
2013-05-27 12:47 ` Tino Keitel
2013-02-07 21:05 ` Paul Gortmaker
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=1354023162.7553.1708.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=Tino.Keitel@alcnetworx.de \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=tino.keitel@tikei.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.