From: Rosen Penev <rosenp@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Marvell 385
Date: Sun, 26 Aug 2018 18:33:45 -0700 [thread overview]
Message-ID: <CAKxU2N8LU+BdVnVqjWn7acw62h+-2uJMhKzaa7Xd-CR1Hj6+cA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7MQF8S_nQLmqmQudZeOXZAcQH5zCL36raFXNCP5RgJ+A@mail.gmail.com>
On Sun, Aug 26, 2018 at 6:20 PM Dave Taht <dave.taht@gmail.com> wrote:
>
> On Sun, Aug 26, 2018 at 5:55 PM Rosen Penev <rosenp@gmail.com> wrote:
> >
> > On Sun, Aug 26, 2018 at 2:09 PM Dave Taht <dave.taht@gmail.com> wrote:
> > >
> > > On Sun, Aug 26, 2018 at 1:58 PM Rosen Penev <rosenp@gmail.com> wrote:
> > > >
> > > > On Sun, Aug 26, 2018 at 11:44 AM Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> > > > >
> > > > > On Sat, 25 Aug 2018, Dave Taht wrote:
> > > > >
> > > > > > The expressobin is a Marvell Armada "3700LP (88F3720) dual core ARM
> > > > > > Cortex A53 processor up to 1.2GHz" - how does that compare? I have
> > > > > > plenty of ath10k and ath9k pcmcia cards....
> > > > >
> > > > > I have one of these, incl wifi. Right now the drivers are not in great
> > > > > shape, but they're being worked on. My espressobin has worse performance
> > > > > than on its wired ports than my WRT1200AC (Armada 385).
> > > > If as you mentioned earlier that ethernet performance is limited by
> > > > interrupts, then this commit is kind of depressing:
> > > >
> > > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/net/ethernet/marvell/mvneta.c?h=next-20180824&id=0f5c6c30a0f8c629b92ecdaef61b315c43fde10a
> > >
> > > I was on that thread. It was broken before entirely. As for the single
> > > interrupt on this chip variant - believe it or not, I'm not huge on
> > > lots of different interrupts for everything. I'd like it if we had
> > > more than an rx or tx interrupt
> > > in general, I'd love it if we had a programmable "tx is almost done"
> > > interrupt that you could tune to the
> > > interrupt latency... and it's complicated and costs wires to have lots
> > > of different interrupt types... and (fantasizing again) I'd love it if
> > > we had a scratchpad or dedicated memory to store interrupt handlers in
> > > rather than relying on cache....
> > >
> > > I'd looked deeply into improving this driver once upon a time, and
> > > wanted to rip the software gro out of it,
> > > in particular, and not defer things as much, trying things like NAPI
> > > of 16 and measuring where time was spent. The copy to memory is
> > > expensive, and then it defers further work.
> > >
> > > Less code, particularly near interrupt time, is better than a lot.
> > > adding XMIT_MORE to the ar71xx driver (which hurt it badly) is one
> > > example.
> > I've been looking a lot at ag71xx. The driver has so much low hanging
> > fruit. Unfortunately I lack the knowledge to fix most of it.
> >
> > This patch for example gives me a ~20-30mbps improvement in iperf
> > tests: https://pastebin.com/ZExWjXQZ
>
> cool! that driver as widely used as it is has never had enough eyeballs on it.
No. Definitely not enough.
>
> Have you put that patch in front of the openwrt folk? I note that that
> driver didn't
> used to live in that part of the tree - have they finally moved over?
Yeah I did. Felix rejected it on the grounds that he didn't understand
it. So I've just been keeping it in my tree. The patch itself comes
from an old SDK by Qualcomm.
>
>
>
> >
> > It's kind of unfortunate given how much atheros hardware is out there.
> > >
> > > Given something *cool* now landing ( skb list batching, see lwn ) it
> > > would be worthwhile to revisit this. I don't care if I get more
> > > interrupts/sec (particularly on a multicore) if we could drain the rx
> > > ring over smaller intervals...
> > >
> > > but that's me, I'm all about the latency. :) Nobody's willing to rip
> > > the latency out of stuff, they'd rather add features. It's really hard
> > > to correctly measure interrupt latency regardless.
> > >
> > >
> > > > >
> > > > > I have talked to people who say the drivers are being worked on though...
> > > > > If you have input, Kaloz is probably a great person to take that input. I
> > > > > know other people working on Marvell drivers as well.
> > > > >
> > > > > --
> > > > > Mikael Abrahamsson email: swmike@swm.pp.se
> > > > > _______________________________________________
> > > > > Bloat mailing list
> > > > > Bloat@lists.bufferbloat.net
> > > > > https://lists.bufferbloat.net/listinfo/bloat
> > >
> > >
> > >
> > > --
> > >
> > > Dave Täht
> > > CEO, TekLibre, LLC
> > > http://www.teklibre.com
> > > Tel: 1-669-226-2619
>
>
>
> --
>
> Dave Täht
> CEO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-669-226-2619
next prev parent reply other threads:[~2018-08-27 1:33 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 0:49 [Bloat] beating the drum for BQL Dave Taht
2018-08-23 5:47 ` Mikael Abrahamsson
2018-08-23 13:06 ` [Bloat] [Cerowrt-devel] " Sebastian Moeller
2018-08-23 13:57 ` Jan Ceuleers
2018-08-23 14:22 ` Sebastian Moeller
2018-08-23 15:32 ` Mikael Abrahamsson
2018-08-23 17:14 ` Rosen Penev
2018-08-23 17:50 ` Mikael Abrahamsson
2018-08-23 18:21 ` Dave Taht
2018-08-23 20:15 ` Dave Taht
2018-08-24 7:00 ` Mikael Abrahamsson
2018-08-24 8:06 ` Dave Taht
2018-08-24 11:22 ` Toke Høiland-Jørgensen
2018-08-24 11:46 ` Jan Ceuleers
2018-08-24 13:43 ` Jan Ceuleers
2018-08-24 13:44 ` Mikael Abrahamsson
2018-08-24 13:56 ` Jan Ceuleers
2018-08-24 13:36 ` Mikael Abrahamsson
2018-08-24 7:05 ` Mikael Abrahamsson
2018-08-24 11:24 ` Toke Høiland-Jørgensen
2018-08-23 21:01 ` Toke Høiland-Jørgensen
2018-08-24 14:44 ` Dave Taht
2018-08-24 17:58 ` Toke Høiland-Jørgensen
2018-08-23 23:35 ` Sebastian Moeller
2018-08-24 1:08 ` David Collier-Brown
2018-08-24 6:16 ` Jan Ceuleers
2018-08-24 11:27 ` Toke Høiland-Jørgensen
2018-08-24 12:46 ` Pedro Tumusok
2018-08-24 13:09 ` Michael Richardson
2018-08-24 13:37 ` Mikael Abrahamsson
2018-08-24 13:44 ` Toke Høiland-Jørgensen
2018-08-26 4:29 ` [Bloat] Marvell 385 Dave Taht
2018-08-26 4:32 ` Jonathan Morton
2018-08-26 16:28 ` Rosen Penev
2018-08-26 18:44 ` Mikael Abrahamsson
2018-08-26 20:53 ` Dave Taht
2018-08-26 20:58 ` Rosen Penev
2018-08-26 21:08 ` Dave Taht
2018-08-27 0:55 ` Rosen Penev
2018-08-27 1:21 ` Dave Taht
2018-08-27 1:33 ` Rosen Penev [this message]
2018-08-27 1:45 ` Dave Taht
2018-08-27 1:53 ` Rosen Penev
2018-08-27 11:33 ` Mikael Abrahamsson
2018-08-23 8:26 ` [Bloat] beating the drum for BQL Pete Heist
2018-08-23 10:51 ` Mikael Abrahamsson
2018-08-23 11:38 ` Pete Heist
2018-08-24 17:13 ` Pete Heist
2018-08-24 17:30 ` Dave Taht
2018-08-24 18:43 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKxU2N8LU+BdVnVqjWn7acw62h+-2uJMhKzaa7Xd-CR1Hj6+cA@mail.gmail.com \
--to=rosenp@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=swmike@swm.pp.se \
/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