Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Dave Täht" <dave.taht@bufferbloat.net>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Working towards reducing memory issues in cerowrt
Date: Thu, 23 Aug 2012 06:58:40 -0700	[thread overview]
Message-ID: <1345730322-6255-1-git-send-email-dave.taht@bufferbloat.net> (raw)

So I was mostly fiddling with codel itself, trying to make it work
better on long RTTs, when the memory and oom issues came up. 

The two patches following for codel are experimental. 

It will take me multiple days to prove out/dismiss as junk and/or further 
improve these... 

During that test cycle I have two patches eric dumazet has suggested on 
the codel list to convinceport/finish/test out, as well as (perhaps) a 
third patch that might control udp better, to deal better with the
memory problem...

... which will need to apply on top of these patches...

so if you are doing your own builds of cero/openwrt or a mainline kernel, 
please feel free to try these and share what, if anything, happens 
differently, on whatever tests you can dream up.


             reply	other threads:[~2012-08-23 13:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-23 13:58 Dave Täht [this message]
2012-08-23 13:58 ` [Cerowrt-devel] [PATCH] codel: Refine re-entering drop state to react sooner Dave Täht
2012-08-23 13:58 ` [Cerowrt-devel] [PATCH 2/2] codel: reduce count after exiting dropping state after one maxpacket Dave Täht
2012-08-23 19:17   ` dpreed
2012-08-24  8:08     ` Dave Taht
2012-08-24 15:29       ` dpreed

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=1345730322-6255-1-git-send-email-dave.taht@bufferbloat.net \
    --to=dave.taht@bufferbloat.net \
    --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