From: Joey Nelson <joey@joescan.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: MPC5200B FEC TX packets getting stuck
Date: Tue, 7 Feb 2012 18:47:04 -0800 [thread overview]
Message-ID: <CAL_WD7jdk78ba9HJ0rYxc1fvVS-PBY4zK6MWhF3H2B_dzFkv_g@mail.gmail.com> (raw)
In-Reply-To: <CAL_WD7hkuhi4D2CPuoLyG2-7w8JmSQDnxiYbqKxzGNep5ONsrg@mail.gmail.com>
I've revisited my testing, and found I was wrong about the packets
getting stuck in the FEC queue. The packets are getting stuck in the
bestcomm.
I generate a timestamp for each skb's ip_hdr->id at the beginning of
mpc52xx_fec_start_xmit, and for each skb retrieved from the bestcomm.
Typically the packets make it through bestcomm in under 200us. But
sometimes a single packet will sit in bestcomm until the next packet
added. In the case of a delayed ACK this can be around 400ms.
When I look at the state of the registers when this condition is
detected (before adding the next bd):
tx_dmatsk->flags = 1
tcr[1] = 0x20c1
Both of these values seem to indicate the the TX task is disabled.
I'm pretty sure that nothing in the kernel is disabling the task, so
it must be an automatic behavior. I notice that
bcom_submit_next_buffer() checks the task->flags and if the LSB is set
it enables the task. So I'm guessing that is what gets things moving
again when the freeze happens.
My best guess is this is a race condition between the driver and the
dma controller. Is there any risk to just calling bcom_enable(tsk).
Maybe after a short sleep.
Joey Nelson
prev parent reply other threads:[~2012-02-08 2:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 20:14 MPC5200B FEC TX packets getting stuck Joey Nelson
2012-02-02 2:33 ` Joey Nelson
2012-02-02 18:43 ` Joey Nelson
2012-02-08 2:47 ` Joey Nelson [this message]
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=CAL_WD7jdk78ba9HJ0rYxc1fvVS-PBY4zK6MWhF3H2B_dzFkv_g@mail.gmail.com \
--to=joey@joescan.com \
--cc=linuxppc-dev@lists.ozlabs.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).