Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	netdev@vger.kernel.org,
	bloat-devel <bloat-devel@lists.bufferbloat.net>,
	Eric Dumazet <eric.dumazet@gmail.com>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: Time in Queue, bufferbloat, and... our accidentally interplanetary network
Date: Wed, 7 Dec 2011 10:59:45 +0100	[thread overview]
Message-ID: <CAA93jw6w1KAUwW0_TTwCuAScMnq1+RUQzLGZsRqPy_txPGbcjw@mail.gmail.com> (raw)
In-Reply-To: <CAJ-VmomuA7u5=zRGMK2Jd3WG+HWTRTZNST4JDVWU9kUEcfE91Q@mail.gmail.com>

On Tue, Dec 6, 2011 at 3:03 AM, Adrian Chadd <adrian@freebsd.org> wrote:
> Hi,
>
> For what it's worth, I've also been tinkering with time-in-queue for
> the wifi queue management in FreeBSD. I don't have anything public
> yet. What I have done actually seems to work quite well, when doing TX
> queue time-in-queue management. (I'm ignoring RX queue management for
> now.)
>
> Yes, I think a weighted random drop with both time-in-queue and queue
> depth would work well. I haven't sat down to model what it'd look like
> given some traffic profiles.
>
> I'll be sure to post some patches and results when I have them. :)

Well, if there is a way to add BQL sanely to the mac80211 or driver
layers and then apply some time in queue techniques at some edge
of some layer(s) down there in Linux, I'd love to know what and where
is good.

It might be simpler to discuss design ideas etc, in a more generic
and less noisy forum than netdev and linux-wireless, at least
for a while, getting to actual patches seems kind of hard at this point.

(at least to me. For all I know eric is finished already, and me, I haven't
 finished grokking the paper he's leveraging some ideas on)

The little I understand about Linux's networking stack dwarfs the
little I know about BSD's, so I look forward to hearing about your
results as you get them, and that said, if you could provide some
pointers and insight into BSD's traffic shaping methods over on
bloat-devel, we do try to be all-architecture embracing in our
attempts to beat the bloat.

>
>
> Adrian



-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
FR Tel: 0638645374
http://www.bufferbloat.net

  reply	other threads:[~2011-12-07  9:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-05  9:05 Dave Taht
2011-12-05 10:59 ` Eric Dumazet
2011-12-06  2:03   ` Adrian Chadd
2011-12-07  9:59     ` Dave Taht [this message]
2011-12-07 10:15   ` [Bloat] " Hagen Paul Pfeifer
2011-12-07 10:19     ` Hagen Paul Pfeifer
2011-12-07 11:53     ` Eric Dumazet
2011-12-08 16:06   ` [PATCH net-next] sch_red: Adaptative RED AQM Eric Dumazet
2011-12-08 17:21     ` Stephen Hemminger
2011-12-08 18:16       ` Eric Dumazet
2011-12-09  0:55     ` David Miller

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw6w1KAUwW0_TTwCuAScMnq1+RUQzLGZsRqPy_txPGbcjw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=adrian@freebsd.org \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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