Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	 "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] another sets of leaps forward for linux packet queueing
Date: Sat, 31 Aug 2013 13:47:50 -0700	[thread overview]
Message-ID: <CAA93jw6ZqyAw5tAywMwTMafyP1qP1GBx_YbocVWbvwm20UF5SQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]

Eric Dumazet just posted a pure fq scheduler (using the highly optimized
red/black trees in the kernel)

http://marc.info/?l=linux-netdev&m=137740009008261&w=2

which "scales to millions of concurrent flows per qdisc".Jon Corbet wrote
it up in (subscriber only link) in lwn http://lwn.net/Articles/564978/
which also details the new tso sizing patch, which fixes the oft complained
about overlarge tso problem and does much saner things with it....

http://thread.gmane.org/gmane.linux.network/281264

Almost simultaneously Stephen Hemminger wrote a sysctl option making it
possible to easily switch the default qdisc from pfifo_fast to "something
else"

http://marc.info/?l=linux-netdev&m=137764555622344&w=2

And earlier in the week Jesper Bauer got the last of the atm/htb fixes in.

All of these patches are now in the net-next tree. There were a few
touchups and tweaks here and there over the days following, that aren't in
there yet...

Future looks so bright we gotta wear shades, or eyepatches, or something....


-- 
Dave Täht

Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html

[-- Attachment #2: Type: text/html, Size: 1757 bytes --]

             reply	other threads:[~2013-08-31 20:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-31 20:47 Dave Taht [this message]
2013-09-06 15:48 ` [Cerowrt-devel] [Codel] " Eric Dumazet

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=CAA93jw6ZqyAw5tAywMwTMafyP1qP1GBx_YbocVWbvwm20UF5SQ@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=codel@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