From: William Katsak <wkatsak@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] better ingress shaping somehow
Date: Thu, 02 Oct 2014 20:57:55 -0400 [thread overview]
Message-ID: <542DF493.80504@gmail.com> (raw)
In-Reply-To: <CAA93jw5Sc0ujnwv-foPQ=iD5Jgfi08RTOR4OCd4t_qbuJ6i2mg@mail.gmail.com>
Do you have a working x86 build for Cero again? Or just playing with a
workstation?
-Bill
On 10/02/2014 07:07 PM, Dave Taht wrote:
> Oh, no, that's an x86 result. It's barely a blip on that cpu use though, so I am
> encouraged so far. Haven't got around to porting it to mips, too many
> non-working ideas elsewhere in it, ENOTIME.
--
****************************************
William Katsak <wkatsak@gmail.com>
****************************************
next prev parent reply other threads:[~2014-10-03 0:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 23:07 Dave Taht
2014-10-03 0:57 ` William Katsak [this message]
2014-10-03 1:26 ` Dave Taht
2014-10-03 18:02 ` Sebastian Moeller
2014-10-05 16:26 ` Richard A. Smith
2014-10-05 17:57 ` Dave Taht
2014-10-06 2:16 ` Richard A. Smith
2014-10-06 2:37 ` Richard A. Smith
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=542DF493.80504@gmail.com \
--to=wkatsak@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