From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net,
Jesper Dangaard Brouer <brouer@redhat.com>,
Felix Fietkau <nbd@nbd.name>
Subject: Re: [Cake] kernel performance analysis in openwrt
Date: Fri, 30 Oct 2015 13:30:17 +0100 [thread overview]
Message-ID: <87r3kcedye.fsf@toke.dk> (raw)
In-Reply-To: <CAA93jw7nHdNzVqYV1bwxNbL3kQwXKc7iQvD_FZ0SyifMmQpCzw@mail.gmail.com> (Dave Taht's message of "Fri, 30 Oct 2015 08:26:02 -0400")
Dave Taht <dave.taht@gmail.com> writes:
> So we are having issues with long term forwarding throughput in cake?
> or just cake on low end processors? Am confused. ?
No issues on x86 that I've noticed. The slowdown is on the Archer.
-Toke
next prev parent reply other threads:[~2015-10-30 12:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 12:26 Dave Taht
2015-10-30 12:30 ` Toke Høiland-Jørgensen [this message]
2015-10-30 14:33 ` Jonathan Morton
2015-10-30 14:34 ` Toke Høiland-Jørgensen
2015-10-30 14:36 ` Kevin Darbyshire-Bryant
2015-10-30 14:43 ` Toke Høiland-Jørgensen
2015-10-30 14:38 ` Jonathan Morton
2015-10-30 15:04 ` Toke Høiland-Jørgensen
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r3kcedye.fsf@toke.dk \
--to=toke@toke.dk \
--cc=brouer@redhat.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=nbd@nbd.name \
/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