Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] SQM in mainline openwrt, fq_codel considered for fedora default
Date: Mon, 20 Oct 2014 10:03:55 -0700	[thread overview]
Message-ID: <CAA93jw4YFUMq=riXA8CYV0Sa2f4sxyxe2DahD0FgKtkayEGKxw@mail.gmail.com> (raw)
In-Reply-To: <121767.1413574248@turing-police.cc.vt.edu>

See:

http://cgit.freedesktop.org/systemd/systemd/commit/?id=e6c253e363dee77ef7e5c5f44c4ca55cded3fd47

There is a scene in Monty Python's "Life of Brian" that comes to mind.
A bunch of revolutionaries are discussing various forms of paper
protest, and world domination, and Judith shows up full of the news
that Brian is being crucified  that day...

"Reg, for God's sake, it's perfectly simple. All you've got to do is
to go out of that door now, and try to stop the Romans' nailing him
up! It's happening, Reg! Something's actually happening, Reg! Can't
you understand?"

Frustrated she leaves the room, and the group takes up a new motion
according to parlamentary rules...

(for the full scene, see: http://www.montypython.net/brianmm3.php )

That's what the last couple years of endless talks and ietf meetings
have felt like....

All that said, doubtless we'll have various snags and difficulties on
the way to more full deployment, various new techniques will appear
and evolve, and

/me goes back to bed whistling "always look on the bright side of life"

On Fri, Oct 17, 2014 at 12:30 PM,  <Valdis.Kletnieks@vt.edu> wrote:
> On Fri, 17 Oct 2014 11:56:01 -0700, Dave Taht said:
>
>> fedora and systemd are considering a change in their distro's default
>> of pfifo_fast to fq_codel:
>>
>> http://osdir.com/ml/general/2014-10/msg34011.html
>
> systemd is a distro now?  Damn, talk about mission creep.. :)



-- 
Dave Täht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks

  reply	other threads:[~2014-10-20 17:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 18:56 Dave Taht
2014-10-17 19:30 ` Valdis.Kletnieks
2014-10-20 17:03   ` Dave Taht [this message]
2014-10-20 17:41     ` Valdis.Kletnieks
2014-10-21 14:50       ` Michal Schmidt
2014-10-21 16:27         ` Valdis.Kletnieks
2014-10-21 16:57           ` Dave Taht
2014-10-21 17:05             ` Michal Schmidt
2014-10-21 17:24               ` Tom Gundersen
2014-10-21 17:44                 ` Michal Schmidt
2014-10-21 17:52                   ` David Personette
2014-10-21 18:00                   ` Michal Schmidt
2014-10-21 18:06                   ` Tom Gundersen
2014-10-21 19:21                     ` Dave Taht
2014-10-21 19:51                       ` Dave Taht
2014-10-21 20:59                         ` Dave Taht
2014-12-04 16:09                           ` Tom Gundersen
2014-12-04 18:24                             ` Dave Taht
2014-10-21 23:18                 ` Toke Høiland-Jørgensen
2014-12-04 15:05                   ` Tom Gundersen
2014-12-04 15:08                     ` Toke Høiland-Jørgensen

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='CAA93jw4YFUMq=riXA8CYV0Sa2f4sxyxe2DahD0FgKtkayEGKxw@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=cerowrt-devel@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