From: rapier <rapier@psc.edu>
To: Valdis.Kletnieks@vt.edu
Cc: web10g-user@web10g.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [Web10g-user] Web10g TCP statistics patch - mainlining into kernel?
Date: Fri, 25 Jan 2013 14:34:57 -0500 [thread overview]
Message-ID: <5102DE61.80804@psc.edu> (raw)
In-Reply-To: <18855.1359138716@turing-police.cc.vt.edu>
Hi,
My name is Chris Rapier and I'm on the Web10G dev team. We are
interested in moving this into consideration for the mainline Linux
kernel, in fact it's the primary goal of this project. We haven't
brought this to the linux kernel community as of yet as we've not
completed the quantification of performance/memory impact versus a
vanilla baseline as of yet. Including the KIS we also have to test the
impact the DKLM imposes (taking into account measurement granularity,
number of concurrent connections, maximum throughput for a single
stream, etc). Then we need to compare that against Web100 and write a
paper. We're looking at around a 2 month time frame for that.
That being said, we welcome any and all insight and help on this that we
can get from the community. Our desire to get the tests and paper worked
out before bringing it to the kernel community was to simply make sure
we would be able to answer any questions that might come up.
Additionally, if you have any metrics of the impact of the KIS, DKLM, or
any combination thereof we'd love to see them. The more data the better
(for some definitions of better).
I and the rest of the development team are more than happy to answer any
questions, address concerns, explain our thinking, discuss possible
applications for this data, etc with anyone interested.
The web100-user list is probably the best way (for us at least) to do
this. You do need to subscribe to post at
https://lists.psc.edu/mailman/listinfo/web10g-user but I'll do my best
to add any relevant posts that get caught up in the filter.
Thanks for your interest and I look forward to talking to anyone
interested in our work.
Chris Rapier
Pittsburgh Supercomputing Center
On 1/25/13 1:31 PM, Valdis Kletnieks wrote:
> 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....
>
>
>
> _______________________________________________
> Web10g-user mailing list
> Web10g-user@web10g.org
> https://lists.psc.edu/mailman/listinfo/web10g-user
>
> To UNSUBSCRIBE visit https://lists.psc.edu/mailman/unsubscribe/web10g-user
>
next prev parent reply other threads:[~2013-01-25 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 18:31 Web10g TCP statistics patch - mainlining into kernel? Valdis Kletnieks
[not found] ` <CAO1dsSdQJDKZ+zzCaLgge9wqiNaJFzPWWBLjRkMEswLVOOd0qA@mail.gmail.com>
2013-01-25 18:57 ` [Web10g-user] " Valdis.Kletnieks
2013-01-25 19:34 ` rapier [this message]
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=5102DE61.80804@psc.edu \
--to=rapier@psc.edu \
--cc=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