From: David Collier-Brown <davec-b@rogers.com>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] QOS on the local network (was: fq_codel is two years old)
Date: Fri, 16 May 2014 22:16:52 -0400 [thread overview]
Message-ID: <5376C694.4080706@rogers.com> (raw)
In-Reply-To: <mailman.3.1400266802.15474.bloat@lists.bufferbloat.net>
Jim Gettys <jg@freedesktop.org> wrote
> Personally, I've mostly been interested in QOS in the local network: as
> "hints", for example, that it is worth more aggressive bidding for transmit
> opportunities in WiFi, for example to ensure my VOIP, teleconferencing,
> gaming, music playing and other actually real time packets get priority
> over bulk data (which includes web traffic), and may need access to the
> medium sooner than for routine applications or scavenger applications.
>
> Whether it should have any use beyond the scope of the network that I
> control is less than clear to me, for the reasons you state; having my
> traffic screw up other people's traffic isn't high on my list of "good
> ideas".
In the days before Jim, Dave et all stuck a spear in bufferbloat, I was
an occasional but happy user of trickle and trickled. Notably where I
had a need to keep a network from overloading a slow up-bound link! See
http://monkey.org/~marius/trickle, and notably .../trickle.pdf
It's probably time to take another look at it as an example of a local
service manager, and as a known functional starting point.
--dave
--
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net | -- Mark Twain
--
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net | -- Mark Twain
parent reply other threads:[~2014-05-17 2:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.3.1400266802.15474.bloat@lists.bufferbloat.net>]
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=5376C694.4080706@rogers.com \
--to=davec-b@rogers.com \
--cc=bloat@lists.bufferbloat.net \
--cc=davecb@spamcop.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