Historic archive of defunct list cerowrt-users@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Maxim Kharlamov <mcs@podsolnuh.biz>
Cc: cerowrt-users@lists.bufferbloat.net,
	cerowrt@lists.bufferbloat.net,
	Jim Reisert AD1C <jjreisert@alum.mit.edu>,
	Stephen Walker <stephendwalker@gmail.com>,
	cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-users] engaging developers and users [#314]
Date: Sat, 17 Dec 2011 09:37:48 +0100	[thread overview]
Message-ID: <CAA93jw7+DXvATrmC1tKVFFgWTbqU+hmu6F5s0WLTmfDE-SqHag@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6aTaKjDp3YBFWdVfgJ-kHTno9Gc_X48EaWqQ6tZOs8Gw@mail.gmail.com>

On Sat, Dec 17, 2011 at 9:30 AM, Dave Taht <dave.taht@gmail.com> wrote:
> On Thu, Dec 15, 2011 at 10:07 AM, Maxim Kharlamov <mcs@podsolnuh.biz> wrote:

> The core difference here at this point between cerowrt and openwrt is the vastly
> reduced tx rings and txqueues - you can add these into openwrt easily by editing
> /etc/init.d/boot to run ethtool at the right time,  and adding
> /etc/hotplug.d/iface/00-debloat to openwrt.

Another core difference is that on cerowrt's wireless, I did much more
extensive
diffserv classification than what's currently in the kernel mainline
and openwrt.

In particular, one thing you can really 'feel' is that stuff with the
IMM bit set
(notably ssh), gets dumped into the VI queue, and that helps ssh a LOT.

Unfortunately that series of patches was terribly hacky and I still haven't
found a good way to rework them for submittal upstream.

You easily get the same behavior for things like ssh via iptables.

      reply	other threads:[~2011-12-17  8:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15  5:14 Dave Taht
2011-12-15  9:07 ` Maxim Kharlamov
2011-12-17  8:30   ` Dave Taht
2011-12-17  8:37     ` Dave Taht [this message]

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=CAA93jw7+DXvATrmC1tKVFFgWTbqU+hmu6F5s0WLTmfDE-SqHag@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=cerowrt-users@lists.bufferbloat.net \
    --cc=cerowrt@lists.bufferbloat.net \
    --cc=jjreisert@alum.mit.edu \
    --cc=mcs@podsolnuh.biz \
    --cc=stephendwalker@gmail.com \
    /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