From: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
web10g-user@web10g.org
Subject: Web10g TCP statistics patch - mainlining into kernel?
Date: Fri, 25 Jan 2013 13:31:56 -0500 [thread overview]
Message-ID: <18855.1359138716@turing-police.cc.vt.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 862 bytes --]
I had a user who's working on tuning high-performance network file systems what
the chances of upstreaming the Web10G patch to provide the RFC4898 TCP Extended
Statistics MIB via netlink.
Yes, it's a tad on the intrusive side, and there's performance costs attached -
but so are a lot of *other* things that people use all the time for kernel
debugging, and it's a zero-hit thing for people who don't choose to configure
it into their kernel. The added detailed status available from this will be
useful for people who are doing tuning and development (consider how useful
this would have been for the people who wrote the codel line discipline as part
of the bufferbloat project).
I'm willing to do the not-so-heavy lifting of getting the existing patch
cleaned up to upstream standards and sheparded through the process, if there's
any interest at all....
[-- Attachment #2: Type: application/pgp-signature, Size: 865 bytes --]
next reply other threads:[~2013-01-25 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 18:31 Valdis Kletnieks [this message]
[not found] ` <CAO1dsSdQJDKZ+zzCaLgge9wqiNaJFzPWWBLjRkMEswLVOOd0qA@mail.gmail.com>
2013-01-25 18:57 ` [Web10g-user] Web10g TCP statistics patch - mainlining into kernel? Valdis.Kletnieks
2013-01-25 19:34 ` rapier
2013-01-25 19:56 ` Valdis.Kletnieks
2013-01-25 20:08 ` rapier
2013-01-25 23:34 ` Tom Herbert
2013-01-29 17:49 ` Ben Hutchings
2013-01-29 18:52 ` David Miller
2013-01-29 19:34 ` [Web10g-user] " rapier
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=18855.1359138716@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=web10g-user@web10g.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).