From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: Maxime Bizon <mbizon@freebox.fr>, Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Advantages to tightly tuning latency
Date: Thu, 23 Apr 2020 16:11:58 -0700 [thread overview]
Message-ID: <CAA93jw4ECsgvjnamqjDFzFboMM9j3u1ZFtF=E8x6zyBOCTJDnw@mail.gmail.com> (raw)
In-Reply-To: <87r1wd6bwy.fsf@toke.dk>
On Thu, Apr 23, 2020 at 4:05 PM Toke Høiland-Jørgensen <toke@redhat.com> wrote:
>
> Maxime Bizon <mbizon@freebox.fr> writes:
>
> > On Thursday 23 Apr 2020 à 20:35:15 (+0200), Toke Høiland-Jørgensen wrote:
> >
> >> I meant more details of your SOC platform. You already said it's
> >> ARM-based, so I guess the most important missing piece is which (Linux)
> >> driver does the Ethernet device(s) use?
> >
> > - Marvell Kirkwood, mv643xx_eth driver
> > - Marvell A8k, mvpp2 driver
>
> No native XDP support in any of those, unfortunately :(
>
> >> Yup, I think so. What does your current solution do with packets that
> >> are destined for the WiFi interface, BTW? Just punt them to the regular
> >> kernel path?
> >
> > yes, but that won't fly anymore for 11ax rates
>
> Indeed, that was partly why I asked :)
> Got any plans?
I would really love to get something going out of this initiative:
https://pointer.ngi.eu/pages/ngi-pointer-opencalls
... either with marvell wifi, 802.11ax, ath11k, mt76... gpon onts,
just something, anything fq-ing at the very least, over fiber of any
sort, would be a start.
is there anyone out there with some spare time and needs some eu dollars?
I tend to disagree that we need massive offloading on 802.11ax. We
need firmware on the chip that does per station scheduling, for the
rest of the queue management a smarter host cpu in the a72 class more
than suffices, especially if the packets are arriving gso'd.
>
> -Toke
>
--
Make Music, Not War
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729
next prev parent reply other threads:[~2020-04-23 23:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 18:22 Justin Kilpatrick
2020-04-21 18:40 ` Jonathan Morton
2020-04-21 18:44 ` Dave Taht
2020-04-21 22:25 ` Thibaut
2020-04-21 22:33 ` Jonathan Morton
2020-04-21 22:44 ` Dave Taht
2020-04-21 22:50 ` Dave Taht
2020-04-21 23:07 ` Jonathan Morton
2020-04-21 23:27 ` Dave Taht
2020-04-22 8:28 ` Thibaut
2020-04-22 9:03 ` Luca Muscariello
2020-04-22 14:48 ` Dave Taht
2020-04-22 15:28 ` Luca Muscariello
2020-04-22 17:42 ` David P. Reed
2020-04-23 9:29 ` Maxime Bizon
2020-04-23 11:57 ` Toke Høiland-Jørgensen
2020-04-23 12:29 ` Luca Muscariello
2020-04-23 12:33 ` Maxime Bizon
2020-04-23 16:42 ` Toke Høiland-Jørgensen
2020-04-23 17:31 ` Maxime Bizon
2020-04-23 18:30 ` Sebastian Moeller
2020-04-23 21:53 ` Maxime Bizon
2020-04-23 18:35 ` Toke Høiland-Jørgensen
2020-04-23 21:59 ` Maxime Bizon
2020-04-23 23:05 ` Toke Høiland-Jørgensen
2020-04-23 23:11 ` Dave Taht [this message]
2020-04-23 16:28 ` Dave Taht
2020-04-21 23:06 ` Justin Kilpatrick
2020-04-21 23:19 ` 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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw4ECsgvjnamqjDFzFboMM9j3u1ZFtF=E8x6zyBOCTJDnw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=mbizon@freebox.fr \
--cc=toke@redhat.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