Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] quick update
Date: Tue, 4 Sep 2012 00:22:29 -0700	[thread overview]
Message-ID: <CAA93jw4PzgDR8JkRWhbZiRJP7Rmgni+yhSChV7cCU=_joNykAA@mail.gmail.com> (raw)

If you can't tell, I have been trying for a stable-ish release of cero
once a month, around the 15th. I'm not sure if I'm going to make it
this time.

Some good things have been happening...

I THINK, but am not sure, the skb shrinkage thing I was doing needs
some headroom added in some cases. I am hoping this would account some
of the introduced flakyness on wifi we encountered in the last dev
release.

This little bit in ath9k/xmit.c looks suspicious:

/* Add the padding after the header if this is not already done */
       padpos = ath9k_cmn_padpos(hdr->frame_control);
       padsize = padpos & 3;
       if (padsize && skb->len > padpos) {
               if (skb_headroom(skb) < padsize)
                       return -ENOMEM;

Also found a few improvements to make to fq_codel at low bandwidths
(below 10Mbit) and something of a theoretical problem with queue
occupancy with tons of flows, and there's been some good threads on
the codel list.

But finding these has been kind of tedious and slow, and my non-bloat,
and trying to make eating money, workload has been a bit much of late.

So I will try to polish up the latest set of cero patches and get them
out there after a great deal more testing on x86.

-- 
Dave Täht

             reply	other threads:[~2012-09-04  7:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-04  7:22 Dave Taht [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-04-28  2:57 Dave Taht

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='CAA93jw4PzgDR8JkRWhbZiRJP7Rmgni+yhSChV7cCU=_joNykAA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --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