From: Dave Taht <dave.taht@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Need more proposals for Linux Plumber's Conference!
Date: Tue, 26 Apr 2011 13:29:57 -0600 [thread overview]
Message-ID: <BANLkTi=-SRGonkDAPn417UhZ5_G-krGJbg@mail.gmail.com> (raw)
In-Reply-To: <20110426174358.GB2804@tuxdriver.com>
I will be meeting with jim after his talk at google today, and perhaps
we can nail a few ideas to the wall.
What did you want your talk to be, john?
Ideas:
1) Beating the Bloat - a progress update from the project
2) Latency matters - the real behavior of voip, gaming, dns, arp, etc,
under Linux today
3) Fixing the embedded Linux software maintenance model
Other suggestions?
next prev parent reply other threads:[~2011-04-26 19:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 17:43 John W. Linville
2011-04-26 19:29 ` Dave Taht [this message]
2011-04-26 20:34 ` John W. Linville
2011-05-01 7:02 ` Dave Taht
2011-05-02 15:13 ` John W. Linville
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='BANLkTi=-SRGonkDAPn417UhZ5_G-krGJbg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=linville@tuxdriver.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