From: Michael Richardson <mcr@sandelman.ca>
To: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] lwn.net's tcp small queues vs wifi aggregation solved
Date: Fri, 22 Jun 2018 10:49:46 -0400 [thread overview]
Message-ID: <25305.1529678986@localhost> (raw)
In-Reply-To: <C03B3E60-FD68-46BC-930F-143879904767@gmail.com>
Jonathan Morton <chromatix99@gmail.com> wrote:
>> Your original note was looking for a way
>> for finding out if the probability of seeing more data in the next 10us
>> was sufficiently large to delay "a teeny bit" so that would be the
>> problem statement.
> I would instead frame the problem as "how can we get hardware to
> incorporate extra packets, which arrive between the request and grant
> phases of the MAC, into the same TXOP?" Then we no longer need to
> think probabilistically, or induce unnecessary delay in the case that
> no further packets arrive.
I've never looked at the ring/buffer/descriptor structure of the ath9k, but
with most ethernet devices, they would just continue reading descriptors
until it was empty. Is there some reason that something similar can not
occur?
Or is the problem at a higher level?
Or is that we don't want to enqueue packets so early, because it's a source
of bloat?
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
next prev parent reply other threads:[~2018-06-22 14:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 4:58 Dave Taht
2018-06-21 9:22 ` Toke Høiland-Jørgensen
2018-06-21 12:55 ` Eric Dumazet
2018-06-21 15:18 ` Dave Taht
2018-06-21 15:31 ` Caleb Cushing
2018-06-21 15:46 ` Stephen Hemminger
2018-06-21 17:41 ` Caleb Cushing
2018-06-21 15:50 ` Dave Taht
2018-06-21 16:29 ` David Collier-Brown
2018-06-21 16:54 ` Jonathan Morton
2018-06-21 16:43 ` Kathleen Nichols
2018-06-21 19:17 ` Dave Taht
2018-06-21 19:41 ` Sebastian Moeller
2018-06-21 19:51 ` Toke Høiland-Jørgensen
2018-06-21 19:54 ` Dave Taht
2018-06-21 20:11 ` Sebastian Moeller
2018-06-22 14:01 ` Kathleen Nichols
2018-06-22 14:12 ` Jonathan Morton
2018-06-22 14:49 ` Michael Richardson [this message]
2018-06-22 15:02 ` Jonathan Morton
2018-06-22 21:55 ` Michael Richardson
2018-06-25 10:38 ` Toke Høiland-Jørgensen
2018-06-25 23:54 ` Jim Gettys
2018-06-26 0:07 ` Jonathan Morton
2018-06-26 0:21 ` David Lang
2018-06-26 0:36 ` Simon Barber
2018-06-26 0:44 ` Jonathan Morton
2018-06-26 0:52 ` Jim Gettys
2018-06-26 0:56 ` David Lang
2018-06-26 11:16 ` Toke Høiland-Jørgensen
2018-06-26 1:27 ` Dave Taht
2018-06-26 3:30 ` Simon Barber
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=25305.1529678986@localhost \
--to=mcr@sandelman.ca \
--cc=bloat@lists.bufferbloat.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