General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: d@taht.net (Dave Täht)
To: "John W. Linville" <linville@tuxdriver.com>
Cc: bloat@bufferbloat.net
Subject: Re: [Bloat] Linux Plumber's Conference CFP is open -- bufferbloat track!
Date: Thu, 17 Mar 2011 15:18:22 -0600	[thread overview]
Message-ID: <8739mlh2e9.fsf@cruithne.co.teklibre.org> (raw)
In-Reply-To: <20110317210702.GC2691@tuxdriver.com> (John W. Linville's message of "Thu, 17 Mar 2011 17:07:02 -0400")


IF I'm still in the country at that point, I can easily talk to:
"Bufferbloat, VOIP and gaming". 

I was originally planning to leave today (:sniff: It's WARM in Mexico, I
keep hitting reload on various websites there) but decided to remain
until at least the end of may and stay intensely focused on bufferbloat
issues. When does one have to commit to a track?

Even if I can't do it, someone else should be able to pick up that topic
and run with it.

Another track idea:

"Building a better router"

"John W. Linville" <linville@tuxdriver.com> writes:

> The Linux Plumber's Conference Call For Papers is open:
>
> 	http://www.linuxplumbersconf.org/2011/linux-plumbers-conference-cfp
>
> I have proposed a Bufferbloat "track":
>
> 	http://www.linuxplumbersconf.org/2011/ocw/events/LPC2011MC/tracks/93
>
> For those unfamiliar with the event, it aims to be a bit different
> from the typical conference.  Instead of the usual collection of
> independent presentations, LPC divides itself into a number of tracks.
> A track usually runs for 2.5 hours, and is composed of related topics
> with less formal presentation requirements.  Often a track is little
> more than a topic introduction followed by lot of freeform discussion.
>
> But...the track won't happen if we don't get some content to fill it!
> My desk is stacked-high with printouts of just a few of the academic
> papers that have been cited on this list, and a know that more than
> a few of the readers are both experienced in public speaking and
> qualified to speak on bufferbloat topics.  So, get busy!
>
> Seriously, please propose a topic and come to Santa Rosa to talk.
> If it is good, I might even buy you some wine! :-)
>
> John
> --
> John W. Linville		Someday the world will need a hero, and you
> linville@tuxdriver.com			might be all we have.  Be ready.
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat

-- 
Dave Taht
http://nex-6.taht.net

  reply	other threads:[~2011-03-17 21:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17 21:07 John W. Linville
2011-03-17 21:18 ` Dave Täht [this message]
     [not found]   ` <87y64dfnft.fsf@cruithne.co.teklibre.org>
2011-03-17 21:34     ` John W. Linville
2011-03-17 21:47       ` Dave Täht
2011-03-18 13:21         ` John W. Linville
2011-03-30 20:28 ` John W. Linville
2011-03-30 21:03   ` Stephen Hemminger

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=8739mlh2e9.fsf@cruithne.co.teklibre.org \
    --to=d@taht.net \
    --cc=bloat@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