netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: rapier <rapier@psc.edu>
To: netdev@vger.kernel.org
Subject: NetDev 0.1 BoF on TCP Stack Instrumentation
Date: Thu, 29 Jan 2015 12:47:52 -0500	[thread overview]
Message-ID: <54CA7248.8090400@psc.edu> (raw)

For those attending the NetDev 0.1 conference in Ottawa this February 
I'll be leading a BoF on TCP stack instrumentation. There is a growing 
understanding of the need for better stack transparency in order to 
diagnose, monitor, and tune TCP flows. This BoF hopes to bring together 
stakeholders and interested parties to determine what instruments 
provide the most value in different use cases, methods for instrument 
implementation, data access methods, and the like.

This BoF is scheduled for two hours in a round table format. I encourage 
any interested party to attend and join in this discussion. I'm looking 
for people and groups currently exploring and invested in this topic to 
help focus the discussion and present their view points. As of this 
moment the agenda for the BoF is flexible. If you'd like to be on the 
agenda and/or make a brief presentation please contact me directly.

Thank you for your interest,

Chris Rapier
Pittsburgh Supercomputing Center
Web10G Project

                 reply	other threads:[~2015-01-29 18:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54CA7248.8090400@psc.edu \
    --to=rapier@psc.edu \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).