Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Pete Heist <pete@heistp.net>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] emulating wifi better - coupling qdiscs in netem?
Date: Mon, 18 Jun 2018 12:44:13 -0700	[thread overview]
Message-ID: <CAA93jw5CYqP9nXR+8cbUfBdQW9VcrD5xSCtvU5mLDDmkyLp6_A@mail.gmail.com> (raw)
In-Reply-To: <B82E0115-0DB4-4CA7-9D3B-5D97880851C5@heistp.net>

On Mon, Jun 18, 2018 at 12:33 PM, Pete Heist <pete@heistp.net> wrote:
>
> On Jun 18, 2018, at 6:08 PM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
>
>
> nfq_set_mode(qh, NFQNL_COPY_PACKET, 0xffff)
>
> ->
>
> nfq_set_mode(qh, NFQNL_COPY_PACKET, 128); // assuming you want to inspect
> headers
>
>
> Thanks for that. I see flat RTTs, and a sometimes significant increase in
> throughputs. Unexpectedly, nfq with GSO throughputs are higher than without
> nfq at all.
>
> ping mean (min-max) RTTs:
>
> APU2, nfq without GSO: 80 us -> 82 us
> APU2, nfq with GSO: 85 us -> 83 us
> 2011 MBP, nfq without GSO: 13 us -> 14 us
> 2011 MBP, nfq with GSO: 14 us -> 13 us
>
> iperf3 throughputs:
>
> APU2, nfq without GSO: 391 -> 415 Mbps
> APU2, nfq with GSO: 3.35 -> 6.07 Gbps [higher than no nfqueue, 5.55 -> 6.07]
> 2011 MBP, nfq without GSO: 1.48 Gbps -> 2.73 Gbps
> 2011 MBP, nfq with GSO: 38.0 Gbps -> 45.5 Gbps [higher than no nfqueue, 39.2
> -> 45.5]

This is still without batch releases, yes?

In any case, the now achieved rates and latencies seem sufficient to
try and adapt these methods to emulating wifi/lte etc better! We only
need to get to a gbit. Obviously doing more expensive userspace
processing is going to hurt, and, well, for the sake of argument
emulating a 32 station wifi 802.11n network would be proof of the
pudding, but I'd settle for even the simplest case of one ap and two
stations
actually rendering sane-looking behavior.

Originally, when thinking about this, I'd thought we'd use one veth
per station and toss packets to userspace based on one nfqueue per
input/output interface. I still lean that way (do we get multicast mac
addrs on packets this way?), but perhaps a single interface could be
used and we could
sort out the src/dst ips and batching in userspace, starting with
fifos to represent current behavior and gradually working our way back
up to the fq_codel on wifi emulation. Or, with one veth per station,
still use a fq_codel qdisc, but I don't see how we can create
backpressure for that actually to engage.

Better to be reordering the verdict on packets in the batch for an
fq_codel emulation. I think.



>
>
>
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast



-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619

  reply	other threads:[~2018-06-18 19:44 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 [this message]
2018-06-18 21:54                         ` Pete Heist
2018-06-18 22:27                           ` Eric Dumazet
2018-06-17 20:42               ` Dave Taht
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=CAA93jw5CYqP9nXR+8cbUfBdQW9VcrD5xSCtvU5mLDDmkyLp6_A@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --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