Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: "David P. Reed" <dpreed@reed.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Ubiquiti QOS
Date: Thu, 29 May 2014 19:40:50 -0400	[thread overview]
Message-ID: <30541.1401406850@sandelman.ca> (raw)
In-Reply-To: <3eb328c9-05fb-4594-81cc-71e6a623b977@katmail.1gravity.com>


David P. Reed <dpreed@reed.com> wrote:
    > ECN-style signaling has the right properties ... just like TTL it can
    > provide

How would you send these signals?

    > A Bloom style filter can remember flow statistics for both of these local
    > policies. A great use for the memory no longer misapplied to
    > buffering....

Well.

On the higher speed dataflow equipment, the buffer is general purpose memory,
so reuse like this is particularly possible.

On routers built around general purpose architectures, the limiting factor
in performance is often memory throughput; adding memory rarely increases
total throughput.   Packet I/O is generally quiet sequential and so makes
good use of wide memory data paths and multiple accesses per address cycle.
Updating of tables such as Bloom filter or any other hash has a big impact
due to the RMW and random access nature.

All I'm saying is that quantity of memory is seldom the problem, but access
to it, is.

I do like the entire idea; it seems that it has to be implemented at the
places where the flow converge, which is often in the DSL line card, or
CTMS...

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


  parent reply	other threads:[~2014-05-29 23:40 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
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 [this message]
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=30541.1401406850@sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@reed.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