From: Dave Taht <dave.taht@gmail.com>
To: Felix Fietkau <nbd@openwrt.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] did a chaos calmer openwrt build, untested
Date: Mon, 16 Mar 2015 12:19:01 -0700 [thread overview]
Message-ID: <CAA93jw65=6cg3mDYCy6CddZNdeYWUUbsXc2=WJvbL6=bwoYdGw@mail.gmail.com> (raw)
In-Reply-To: <550726B8.2060807@openwrt.org>
[-- Attachment #1: Type: text/plain, Size: 1957 bytes --]
On Mon, Mar 16, 2015 at 11:53 AM, Felix Fietkau <nbd@openwrt.org> wrote:
> On 2015-03-16 17:58, Dave Taht wrote:
> > I folded in the following:
> >
> > * minstrel-blues
> As far as I know, this is not really "minstrel-blues", this is a minor
> set of minstrel tweaks.
>
> > * minstrel patches for minimum variance (hurts udp, helps tcp)
> Is this the same patches that you sent a while back?
>
> Yes. They did leverage a function call from the above.
> > * babel-1.6.0 release candidate
> > * cake and the usual slew of alternate bufferbloat-fighting qdiscs
> >
> > I intended to use this build to test my ubnt gear and the archer c7v2.
> > It is NOT cerowrt...
> >
> > http://snapon.lab.bufferbloat.net/~cero3/ubnt/ar71xx/
> Where's the source? I can't find it on your github...
>
>
One of my goals is to work more closely within openwrt's structures this
time around,
I only did that build because half my campus network is breaking on a
regular basis and I have *gotta* fix that.
> 1) But before I even got so far as trying that build, ran across this
> > ticket.
> >
> > https://dev.openwrt.org/ticket/19194
> Haven't seen any similar reports from other people yet, might be a
> device specific quirk or broken hw or something, I don't know yet.
>
> > 2) Is the consensus here we should resume using the "device naming by
> > security model" mode?
> >
> > 3) Things I would like to be developing and then testing
> > * latest dnsmasq code (with fixed date getting stuff to hopefully
> > finally make it up to openwrt)
> > * latest FIB patches backported to 3.18 (or, possibly, moving to 4.0)
> The FIB patches that went into 4.0 are already in OpenWrt trunk ;)
>
Would like to update the ar71xx code also, if possible?
> - Felix
>
--
Dave Täht
Let's make wifi fast, less jittery and reliable again!
https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
[-- Attachment #2: Type: text/html, Size: 3446 bytes --]
prev parent reply other threads:[~2015-03-16 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 16:58 Dave Taht
[not found] ` <550711A0.1080706@midlink.org>
2015-03-16 17:30 ` Dave Taht
2015-03-16 18:53 ` Felix Fietkau
2015-03-16 19:19 ` 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
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='CAA93jw65=6cg3mDYCy6CddZNdeYWUUbsXc2=WJvbL6=bwoYdGw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=nbd@openwrt.org \
/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