From: "Leonidas P. Papadakos" <papadakospan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Peter Geis <pgwipeout-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: ayufan-1nXcilf+G7OHXe+LvDLADg@public.gmane.org,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>,
Thomas McKahan
<tonymckahan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH v2] arm64: dts: rockchip: fix rk3328-roc-cc gmac2io tx/rx_delay
Date: Wed, 13 Mar 2019 22:20:01 +0200 [thread overview]
Message-ID: <1552508401.2008.0@gmail.com> (raw)
In-Reply-To: <20190310002636.GA3857@X555LD>
Στις Κυρ, 10 Μαρ, 2019 at 2:26 ΠΜ, ο/η "Leonidas P.
Papadakos" <papadakospan@gmail.com> έγραψε:
>> > > We have several issues on the rk3328.
>> > >
>> > > The first issue, which you describe as the ssh lag, is the
>> > > tx-offload issue.
>> > > Packets that are larger than the MTU and will be fragmented
>> break if
>> > > tx-offload is enabled.
>> > > To fix this, you must somehow disable tx-offload.
>> > > force-thresh-dma-mode disabled tx-offload, but had other side
>> effects.
>> > > Ayufan's patch disables tx-offload only if the packet is larger
>> than
>> > > 1498.
>> > > You can also disable tx-offload from userspace with ethtool.
>> > >
>> > > The second issue is the high rate of tx packets being corrupted,
>> > > which my patch to set the tx pull values fixes.
>> > >
>> > > The third issue is the tx and rx delays need to be tuned now
>> that
>> > > the tx packet corruption issue has been fixed.
>> > >
>> > > I hope this clears things up a little for you.
>> >
>> > Yup, that's what I have in my mind already. My previous comment
>> wasn't
>> > clear, I know.
>> > I pieced it together after your dma-mode patch, because that one
>> fixed
>> > the ssh lag.
>> > My previous email was just what I saw after those changes.
>> >
>> > In my case the link reset still happens with your patch.
>> >
>> > You're thinking that the combination of your patch, ayufan's
>> > "conditional" patch and a specific tweak in the delays would work
>> for
>> > the network instability problem?
>> >
>>
>> Correct, the link-reset tends to happen when the delays are at the
>> edge of
>> working.
>> There is also the possibility that board level manufacturing
>> tolerances are
>> causing issues where the delay can change between boards.
>> If this is the case, we will have to make an auto-tune function,
>> probably
>> based off the mmc version.
>
> So, I tried just your patch with archlinuxARM linux 5.0
> (meaning the tx/rx_delays are 0x25/0x11 respectively if I'm not
> mistaken)
> and disabled tx offload through ethtool.
>
> After 3 30-second iperf3 tests, no link resets! I get about the same
> speed you mentioned before,
> 800-something to 700-something lowest.
>
> Seems like the delays that are already there in the dts are better
> than the ones I picked up from the Armbian dts.
>
> It's worth noting that I've never noticed a link reset in my ~3
> months of using the 4.4 Rockchip kernel
> that Armbian packages using ayufan's linux-kernel repo. Maybe
> something there?
>
> All in all, it does seem to be much better with your patch.
I've been trying to reach ayufan about his patch, getting is into
mainline:
https://github.com/ayufan-rock64/linux-mainline-kernel/commit/41eeb7cd789ea7cac0cbf4b35b53055f354da757
but it seems he's not responding. I'll cc him.
His patch would be a really cool fix if it could be in 5.1, or even 5.2,
as a replacement to force_thresh_dma_mode
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2019-03-13 20:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 22:34 [PATCH v2] arm64: dts: rockchip: fix rk3328-roc-cc gmac2io tx/rx_delay Leonidas P. Papadakos
[not found] ` <20190306223454.2959-1-papadakospan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-03-06 22:37 ` Leonidas P. Papadakos
2019-03-08 1:05 ` Peter Geis
[not found] ` <24c5ffaa-644d-4623-a635-6842f67efe8a-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-03-08 1:27 ` Leonidas P. Papadakos
[not found] ` <1552008447.3271.0-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-03-08 23:26 ` Leonidas P. Papadakos
[not found] ` <1552087603.1401.0-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-03-09 2:39 ` Peter Geis
[not found] ` <ec810aad-dd04-84e4-bfb0-98b005cf3f03-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-03-09 3:26 ` Leonidas P. Papadakos
[not found] ` <1552101990.1401.3-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-03-09 12:45 ` Peter Geis
[not found] ` <e9c539ce-f1cb-06f8-1083-ea64c9fd9e7b-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-03-09 14:16 ` Heiko Stuebner
2019-03-09 14:21 ` Peter Geis
[not found] ` <4f17a798-ed28-8403-ed75-30fdf4bfc44b-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-03-09 23:05 ` Leonidas P. Papadakos
[not found] ` <1552172735.1238.0-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-03-09 23:16 ` Peter Geis
[not found] ` <1bab9d4c-5e9d-968d-026d-98e65af6e7ee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-03-09 23:25 ` Leonidas P. Papadakos
[not found] ` <1552173935.1238.1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-03-09 23:34 ` Peter Geis
[not found] ` <6d6a700a-39c9-25b6-dfff-296c0757603d-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-03-10 0:26 ` Leonidas P. Papadakos
2019-03-13 20:20 ` Leonidas P. Papadakos [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=1552508401.2008.0@gmail.com \
--to=papadakospan-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=ayufan-1nXcilf+G7OHXe+LvDLADg@public.gmane.org \
--cc=heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=pgwipeout-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=tonymckahan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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