From: Dave Taht <dave.taht@gmail.com>
To: David Lang <david@lang.hm>, Jesper Dangaard Brouer <brouer@redhat.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] bulk packet transmission
Date: Thu, 9 Oct 2014 12:48:35 -0700 [thread overview]
Message-ID: <CAA93jw7wW5GffuRhE=pjDsrkBGep6j-L7DpAQdoQz2xLUNZuLw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1410091238190.23992@nftneq.ynat.uz>
I have some hope that the skb->xmit_more API could be used to make
aggregating packets in wifi on an AP saner. (my vision for it was that
the overlying qdisc would set xmit_more while it still had packets
queued up for a given station and then stop and switch to the next.
But the rest of the infrastructure ended up pretty closely tied to
BQL....)
Jesper just wrote a nice piece about it also.
http://netoptimizer.blogspot.com/2014/10/unlocked-10gbps-tx-wirespeed-smallest.html
It was nice to fool around at 10GigE for a while! And netperf-wrapper
scales to this speed also! :wow:
I do worry that once sch_fq and fq_codel support is added that there
will be side effects. I would really like - now that there are al
these people profiling things at this level to see profiles including
those qdiscs.
/me goes grumbling back to thinking about wifi.
On Thu, Oct 9, 2014 at 12:40 PM, David Lang <david@lang.hm> wrote:
> lwn.net has an article about a set of new patches that avoid some locking
> overhead by transmitting multiple packets at once.
>
> It doesn't work for things with multiple queues (like fq_codel) in it's
> current iteration, but it sounds like something that should be looked at and
> watched for latency related issues.
>
> http://lwn.net/Articles/615238/
>
> David Lang
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
https://www.bufferbloat.net/projects/make-wifi-fast
next prev parent reply other threads:[~2014-10-09 19:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 19:40 David Lang
2014-10-09 19:48 ` Dave Taht [this message]
2014-10-11 0:52 ` dpreed
2014-10-11 3:15 ` David Lang
2014-10-11 4:20 ` David P. Reed
2014-10-13 22:11 ` Dave Taht
2014-10-15 19:49 ` Wes Felter
2014-10-15 22:41 ` dpreed
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw7wW5GffuRhE=pjDsrkBGep6j-L7DpAQdoQz2xLUNZuLw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=brouer@redhat.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=david@lang.hm \
/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