From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux1394-devel@lists.sourceforge.net,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] firewire: net: rate-limit log spam at transmit failure
Date: Sun, 07 Nov 2010 05:32:17 +0200 [thread overview]
Message-ID: <1289100737.3277.32.camel@maxim-laptop> (raw)
In-Reply-To: <1289100404.3277.28.camel@maxim-laptop>
[-- Attachment #1: Type: text/plain, Size: 1979 bytes --]
On Sun, 2010-11-07 at 05:26 +0200, Maxim Levitsky wrote:
> On Sun, 2010-11-07 at 00:23 +0100, Stefan Richter wrote:
> > On 6 Nov, Stefan Richter wrote:
> > > Then I tried an XIO2213A card in the AMD PC (again the Intel PC as peer)
> > > and got 243 times "failed: 12" i.e. RCODE_BUSY and 81 times "failed: 10"
> > > i.e. RCODE_SEND_ERROR during ftp transfer of a >500 MB large file from
> > > XIO2213A to FW323.
> >
>
> I also am getting strange results (but very good compared to what I had
> recently).
>
> With all your patches, I get very stable TCP and UDP streams from laptop
> to desktop at 180~190 Mbits/s.
>
> However, the opposite direction (desktop->laptop) still suffers from
> tlabel exhaustion.
> I added some printks, and I see, clearly that netif_stop_queue doesn't
> always work (probably this is intended?).
>
> If I replace == with >= in inc_queue_packets and similar in
> dec_queued_packets, then tlabel exhaustion disappears, and I get ~240
> Mbit/s on TCP and UDP.
>
> UDP transfers work quite well, tested for few minutes.
> TCP transfers unfortunelly trigger (probably a hardware) bug in notebook
> OHCI controller (I have seen that meny times so far.)
>
> Transfer just stops, and controller goes south.
> If I unload the firewire-ohci, then when I load it:
>
> [ 2062.632532] firewire_ohci 0000:07:00.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
> [ 2072.650173] firewire_ohci: Failed to reset ohci card.
> [ 2072.650267] firewire_ohci 0000:07:00.0: PCI INT A disabled
> [ 2072.650314] firewire_ohci: probe of 0000:07:00.0 failed with error -16
>
>
> Only suspend to ram helps bring it back from that state.
>
> Best regards,
> Maxim Levitsky
>
To be clear, I use patches I attached on top of today mainline.
I have here my own hack to set the transaction timeout, because
update_split_timeout isn't called here at all, because nobody writes
to corresponding CSR registers.
Maybe I miss something though.
Best regards,
Maxim Levitsky
[-- Attachment #2: patches.tar.bz2 --]
[-- Type: application/x-bzip-compressed-tar, Size: 4498 bytes --]
next prev parent reply other threads:[~2010-11-07 3:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tkrat.01ca17fba0508ae0@s5r6.in-berlin.de>
[not found] ` <tkrat.1b9925fa1d199c23@s5r6.in-berlin.de>
[not found] ` <tkrat.18b9f67ac78dcbea@s5r6.in-berlin.de>
[not found] ` <tkrat.276aeae22ec60090@s5r6.in-berlin.de>
2010-11-07 3:26 ` [PATCH] firewire: net: rate-limit log spam at transmit failure Maxim Levitsky
2010-11-07 3:32 ` Maxim Levitsky [this message]
2010-11-07 12:03 ` Stefan Richter
2010-11-08 1:41 ` Maxim Levitsky
2010-11-08 8:12 ` Stefan Richter
2010-11-07 11:10 ` Stefan Richter
2010-11-07 12:04 ` Maxim Levitsky
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=1289100737.3277.32.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.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 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).