From: rapier <rapier@psc.edu>
To: David Miller <davem@davemloft.net>, alexei.starovoitov@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 2/3] Implementation of RFC 4898 Extended TCP Statistics (Web10G)
Date: Tue, 16 Dec 2014 15:01:49 -0500 [thread overview]
Message-ID: <54908FAD.5060500@psc.edu> (raw)
In-Reply-To: <20141216.140919.44020047339373813.davem@davemloft.net>
On 12/16/14, 2:09 PM, David Miller wrote:
> From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
> Date: Tue, 16 Dec 2014 10:24:31 -0800
>
>> imo that is very questionable design choice.
>> export a lot of in-kernel bits to be used by out-of-tree kernel module?
>
> It's a non-starter.
Understood. We're in the process of reviewing which symbols are required
by the DLKM we've provided and which are required by in tree modules
(e.g tcp_estats_enabled is required by tcp_htcp). In the meantime, I do
want to stress that the KIS is distinct from the control and management
functions in this patch. We'd like to make sure that problems with this
patch aren't negating the value of the instrument set.
next prev parent reply other threads:[~2014-12-16 20:01 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 [this message]
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
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=54908FAD.5060500@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).