From: Valdis.Kletnieks@vt.edu
To: Dane Medic <dm70dm@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Ubiquiti QOS
Date: Sun, 25 May 2014 10:23:03 -0400 [thread overview]
Message-ID: <211075.1401027783@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sun, 25 May 2014 08:17:47 +0200." <CABsdH_FMqARQQ7oT2gGE6PEZWk1E6b6CDGdBH958nL2=FmFv-A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
On Sun, 25 May 2014 08:17:47 +0200, Dane Medic said:
> Is it true that devices with less than 64 MB can't handle QOS? ->
> https://lists.chambana.net/pipermail/commotion-dev/2014-May/001816.html
I'm not going to give one post on a list very much credence, especially when
it doesn't contain a single actual fact or definitive claim. An explanation
of exactly which data structure won't fit in 32M would be ideal. Even some
numbers on RAM usage from /proc/slabinfo and a "who ate all the frobozz slabs?"
would be better than what's in the post.
[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]
next prev parent reply other threads:[~2014-05-25 14:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-25 6:17 Dane Medic
2014-05-25 14:23 ` Valdis.Kletnieks [this message]
2014-05-25 15:42 ` Mikael Abrahamsson
2014-05-25 20:00 ` dpreed
2014-05-26 0:18 ` Mikael Abrahamsson
2014-05-26 4:49 ` dpreed
2014-05-26 13:02 ` Mikael Abrahamsson
2014-05-26 14:01 ` dpreed
2014-05-26 14:11 ` Mikael Abrahamsson
2014-05-26 15:31 ` David P. Reed
2014-05-27 21:19 ` David Lang
2014-05-27 22:00 ` Dave Taht
2014-05-27 23:27 ` David Lang
2014-05-28 2:12 ` Dave Taht
2014-05-28 3:21 ` David Lang
2014-05-28 15:52 ` dpreed
2014-05-28 16:34 ` David Lang
2014-05-27 15:23 ` Jim Gettys
2014-05-27 17:31 ` Dave Taht
2014-05-28 15:33 ` dpreed
2014-05-28 15:20 ` dpreed
2014-05-28 18:33 ` David Lang
2014-05-29 12:11 ` David P. Reed
2014-05-29 15:29 ` dpreed
2014-05-29 19:30 ` David Lang
2014-05-29 23:40 ` Michael Richardson
2014-05-30 0:32 ` David P. Reed
2014-05-30 0:36 ` Dave Taht
2014-05-25 18:39 ` Sebastian Moeller
2014-05-25 19:33 ` 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=211075.1401027783@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dm70dm@gmail.com \
/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