From: rapier <rapier@psc.edu>
To: netdev <netdev@vger.kernel.org>
Subject: TCP Stack Instrumentation Mailing List
Date: Thu, 19 Feb 2015 17:26:39 -0500 [thread overview]
Message-ID: <54E6631F.2040908@psc.edu> (raw)
All,
At the recent NetDev conference we had BoF on TCP stack instrumentation.
The general consensus is that it's a good idea and worth pursuing. We've
decided to start a mailing list to discuss design goals and
implementation. If you have any interest in what's happening in the
stack, ideas, and/or would like to help out you can join at
tcpinst-wg@psc.edu
or
https://lists.psc.edu/mailman/listinfo/tcpinst-wg
Thanks!
Chris
reply other threads:[~2015-02-19 22:26 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=54E6631F.2040908@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).