linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tirumala Marri <tmarri@apm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Prashant Bhole <prashantsmailcenter@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: RE: ibm_newemac tx problem with jumbo frame enabled
Date: Thu, 8 Dec 2011 15:11:47 -0800	[thread overview]
Message-ID: <b6948354f389d3b585d95cb9eab05b70@mail.gmail.com> (raw)
In-Reply-To: <1323385148.19891.5.camel@pasglop>

Hi Ben,

>-----Original Message-----
>From: Benjamin Herrenschmidt [mailto:benh@kernel.crashing.org]
>Sent: Thursday, December 08, 2011 2:59 PM
>To: Prashant Bhole
>Cc: linuxppc-dev@ozlabs.org; Tirumala Marri
>Subject: Re: ibm_newemac tx problem with jumbo frame enabled
>
>On Thu, 2011-12-08 at 18:31 +0530, Prashant Bhole wrote:
>
>>
>> I checked RX descriptor status and TX descriptor status and ethtool
>> output.
>> However I don't know about pause packet/frame, how do I check if pause
>> frames are properly negotiated on both sides?
>> I need to try changing pause and FIFO thresholds.
>>
>> ethtool output after disconnection is as follows:
>> # ethtool -S eth0
>> NIC statistics:
>>      rx_packets: 330939
>>      rx_bytes: 804963241
>>      tx_packets: 248554
>>      tx_bytes: 798853638
>>      rx_packets_csum: 330716
>>      tx_packets_csum: 179526
>>      tx_undo: 0
>
> .../...
>
>Ok so none of the error counters seem to trip, odd. No idea what's up,
>you may want to ask the folks at APM (CCed Tirumala).
>
>I wonder also if we are properly enabling the reporting of error
>interrupts... if we got that wrong we may never detect FIFO overruns.
>What you describe really looks like a fifo overrun to me.
>
>Additionally, look at emac_configure(), sees how it configures the pause
>packet thresholds, maybe you can tweak the watermark to be more
>aggressive. Also check that pause is actually enabled (with ethtool) and
>that the PHY negociated it properly (that the link partner supports
>pause frames).
>
I will take a look.
Thx,
Marri

      reply	other threads:[~2011-12-08 23:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18  5:03 ibm_newemac tx problem with jumbo frame enabled Prashant Bhole
2011-11-25  5:25 ` Benjamin Herrenschmidt
2011-12-07  8:05   ` Prashant Bhole
2011-12-07 22:03     ` Benjamin Herrenschmidt
2011-12-08 13:01       ` Prashant Bhole
2011-12-08 22:59         ` Benjamin Herrenschmidt
2011-12-08 23:11           ` Tirumala Marri [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=b6948354f389d3b585d95cb9eab05b70@mail.gmail.com \
    --to=tmarri@apm.com \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=prashantsmailcenter@gmail.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).