From: Leen Besselink <bufferbloat@consolejunkie.net>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Improving the murray hill's presentation
Date: Tue, 8 Feb 2011 19:42:12 +0100 [thread overview]
Message-ID: <20110208184207.GA9789@apia.perrit.net> (raw)
In-Reply-To=<871v3tcbwg.fsf@cruithne.co.teklibre.org>
Hi,
This is my first post to the mailinglists, I've been reading everything most of what
Jim Gettys has been writing and trying to wrap my head around the problem.
Maybe this is a silly idea, but I think it would really illustrate to those 'in the know'
if we change the frontpage of the bufferbloat-site.
My idea wass to put the before and after SmokePing graphics from the presentation (PDF-page 62
and 63) on the frontpage.
Hopefully with a short & sweet explanation and a way to encourages people also to look y-axis,
the labels and packetloss.
Maybe that will drive home that their is a problem.
Hope this is helpful.
Have a nice day,
Leen.
next reply other threads:[~2011-02-08 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 18:42 Leen Besselink [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-31 15:48 Dave Täht
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110208184207.GA9789@apia.perrit.net \
--to=bufferbloat@consolejunkie.net \
--cc=bloat@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