Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Jim Gettys <jg@freedesktop.org>
To: Matt Taggart <matt@lackof.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Glossary wiki page
Date: Sat, 4 Oct 2014 17:08:11 -0700	[thread overview]
Message-ID: <CAGhGL2CNQH_bY3hE78ax8JDRXjk6Z6gcp5Z49uih0ebsLVF0uQ@mail.gmail.com> (raw)
In-Reply-To: <20141004222240.B1D771BB@taggart.lackof.org>

[-- Attachment #1: Type: text/plain, Size: 1765 bytes --]

Both bufferbloat.net and wikipedia are wiki's for a reason...  Don't be too
shy, Matt ;-).
                            - Jim


On Sat, Oct 4, 2014 at 3:22 PM, Matt Taggart <matt@lackof.org> wrote:

> Hi cerowrt-devel,
>
> The Glossary at
>   http://www.bufferbloat.net/projects/bloat/wiki/Glossary
> is pretty sparse and needs some editing, here are some suggestions:
>
> Probably thanks to the effort of people on this list, Wikipedia (now) has a
> bunch of good pages, lists of terminology, queuing disciplines,
> bufferbloat, etc
>
> I think it's still useful to have some definitions in the Glossary, but
> maybe it can now refer to wikipedia pages for a lot of things (and if
> needed more things could be added to wikipedia).
>
> Good general jumping off point
> https://en.wikipedia.org/wiki/Network_scheduler
>
> The wikipedia 'network performance' category, lists lots of things that
> might be worth describing
> https://en.wikipedia.org/wiki/Category:Network_performance
>
> In particular, here are links from things that the glossary already
> mentions or might want to
> https://en.wikipedia.org/wiki/Throughput
> https://en.wikipedia.org/wiki/Throughput#Channel_utilization_and_efficiency
> https://en.wikipedia.org/wiki/Quality_of_service
> https://en.wikipedia.org/wiki/Queueing_theory
> https://en.wikipedia.org/wiki/Rate_limiting
> https://en.wikipedia.org/wiki/Goodput
> https://en.wikipedia.org/wiki/Explicit_Congestion_Notification
> https://en.wikipedia.org/wiki/CoDel
> https://en.wikipedia.org/wiki/Bufferbloat
>
> Thanks,
>
> --
> Matt Taggart
> matt@lackof.org
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

[-- Attachment #2: Type: text/html, Size: 3633 bytes --]

      reply	other threads:[~2014-10-05  0:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-04 22:22 Matt Taggart
2014-10-05  0:08 ` Jim Gettys [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=CAGhGL2CNQH_bY3hE78ax8JDRXjk6Z6gcp5Z49uih0ebsLVF0uQ@mail.gmail.com \
    --to=jg@freedesktop.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=matt@lackof.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