From: rapier <rapier@psc.edu>
To: David Miller <davem@davemloft.net>
Cc: alexei.starovoitov@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 2/3] Implementation of RFC 4898 Extended TCP Statistics (Web10G)
Date: Tue, 16 Dec 2014 16:02:13 -0500 [thread overview]
Message-ID: <54909DD5.5070202@psc.edu> (raw)
In-Reply-To: <20141216.151823.2276708539799601894.davem@davemloft.net>
On 12/16/14 3:18 PM, David Miller wrote:
> From: rapier <rapier@psc.edu>
> Date: Tue, 16 Dec 2014 15:13:44 -0500
>
>> On 12/16/14, 3:03 PM, David Miller wrote:
>>
>>> You shouldn't need to export any symbols.
>>
>> As a point of clarification - is it acceptable to export symbols for
>> use with in tree modules such as tcp_htcp? We are more than willing to
>> do the work required to bring this in line with best practices.
>
> I'm saying for data and TCP statistics collection, you shouldn't need
> to add any new symbol exports.
We've been able to identify that as the code stands we only need one
export for the KIS. That being said, I understand if that's one too
many. The DLKM (which hasn't been submitted) does require two additional
symbols and that's an oversight on our part. We'll work to eliminate
those as well.
> Keep this in the main kernel, nothing external should be needed.
>
> Extending tcp_info or similar is the only reasonable way to implement
> this stuff.
I understand where you are coming from. I do believe that our
methodology provides some advantages over a tcp_info solution. I'll
provide some information on that tomorrow after I've had a chance to
talk about this in more depth with our dev team. That being said, we
only really care about the instrument set being incorporated as such we
will take a closer look tcp_info shortly.
Chris
next prev parent reply other threads:[~2014-12-16 21:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 18:24 [PATCH net-next 2/3] Implementation of RFC 4898 Extended TCP Statistics (Web10G) Alexei Starovoitov
2014-12-16 18:58 ` rapier
2014-12-16 19:11 ` David Miller
2014-12-16 19:09 ` David Miller
2014-12-16 20:01 ` rapier
2014-12-16 20:03 ` David Miller
2014-12-16 20:13 ` rapier
2014-12-16 20:18 ` David Miller
2014-12-16 21:02 ` rapier [this message]
2014-12-16 22:33 ` Eric Dumazet
2014-12-16 22:44 ` David Miller
2014-12-17 17:32 ` rapier
2014-12-16 22:09 ` Dominic Hamon
-- strict thread matches above, loose matches on Subject: below --
2014-12-16 17:50 rapier
2014-12-17 3:44 ` Andi Kleen
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=54909DD5.5070202@psc.edu \
--to=rapier@psc.edu \
--cc=alexei.starovoitov@gmail.com \
--cc=davem@davemloft.net \
--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).