From: Dave Taht <dave.taht@gmail.com>
To: Pete Heist <pete@heistp.net>
Cc: Jesper Dangaard Brouer <brouer@redhat.com>,
Florian Westphal <fw@strlen.de>,
Marek Majkowski <marek@cloudflare.com>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] emulating wifi better - coupling qdiscs in netem?
Date: Sun, 17 Jun 2018 13:42:43 -0700 [thread overview]
Message-ID: <CAA93jw7VEfYnz0Z2Z2poovm2wnqXx-gfVd-XF6_V=P=CBJ_W5A@mail.gmail.com> (raw)
In-Reply-To: <EF6AF7D1-471C-437B-8CF2-2FDDC9D83DE6@heistp.net>
On Sun, Jun 17, 2018 at 11:38 AM, Pete Heist <pete@heistp.net> wrote:
>
>> On Jun 17, 2018, at 6:09 PM, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> I'm pleased that these are apu2 results, I have some hope that a
>> heftier box can do better.
>
> I suspect 10-20x is possible on more modern, desktop class hardware.
I appreciate the optimism, but it's context switch time that dominates
here which does not scale.
>> And these are not using the bulk verdict facility?
>
> It looks like not to me. nfq_nlmsg_verdict_put is called with a single ID and I see no references to the batch verdict support there. > Presumably there are significant gains to be had there.
But: I have high hopes for the batch verdict capability, we issue a
verdict for that batch, then (wait the actual time to simulated-ly
deliver an wifi aggregate - projected cpu latency), then release the
next batch. this seems to me to be able to overlap and ignore the bus
arbitration step almost entirely.
I'll get on this myself after I'm done with the cake talk next week.
Thx for the thoughts and evaluations!
(still wish I could do it in-kernel)
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
next prev parent reply other threads:[~2018-06-17 20:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 17:28 Dave Taht
2018-05-30 18:32 ` Bob McMahon
2018-05-30 18:54 ` Dave Taht
2018-05-30 18:58 ` Jonathan Morton
2018-05-30 19:19 ` Bob McMahon
2018-05-30 23:26 ` Dave Taht
2018-05-30 22:57 ` dpreed
2018-06-15 22:30 ` Dave Taht
2018-06-16 22:53 ` Pete Heist
2018-06-17 11:19 ` Jesper Dangaard Brouer
2018-06-17 15:16 ` Pete Heist
2018-06-17 16:09 ` Dave Taht
2018-06-17 18:38 ` Pete Heist
2018-06-17 18:47 ` Jonathan Morton
2018-06-18 9:24 ` Pete Heist
2018-06-18 16:08 ` Eric Dumazet
2018-06-18 19:33 ` Pete Heist
2018-06-18 19:44 ` Dave Taht
2018-06-18 21:54 ` Pete Heist
2018-06-18 22:27 ` Eric Dumazet
2018-06-17 20:42 ` Dave Taht [this message]
2018-06-18 1:02 ` Eric Dumazet
2018-06-18 0:59 ` Eric Dumazet
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw7VEfYnz0Z2Z2poovm2wnqXx-gfVd-XF6_V=P=CBJ_W5A@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=brouer@redhat.com \
--cc=fw@strlen.de \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=marek@cloudflare.com \
--cc=pete@heistp.net \
/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