From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: Valdis.Kletnieks@vt.edu, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, web10g-user@web10g.org
Subject: Re: Web10g TCP statistics patch - mainlining into kernel?
Date: Tue, 29 Jan 2013 13:52:22 -0500 (EST) [thread overview]
Message-ID: <20130129.135222.864358079580838703.davem@davemloft.net> (raw)
In-Reply-To: <1359481755.4144.4.camel@bwh-desktop.uk.solarflarecom.com>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Tue, 29 Jan 2013 17:49:15 +0000
> On Fri, 2013-01-25 at 13:31 -0500, Valdis Kletnieks wrote:
> [...]
>> it's a zero-hit thing for people who don't choose to configure
>> it into their kernel.
> [...]
>
> People with high-overhead changes always say this, but before long
> distributions will be expected to enable it and then everyone pays the
> price. So I think you'll have to work on limiting the run-time overhead
> when it's enabled at compile time but the user doesn't care about it.
> Possibly it can be a run-time option? (I haven't looked at the code and
> don't expect to have time to do so.)
+1
The run time overhead must be zero when the feature is configured into
the kernel, and this requirement is non-negotiable.
next prev parent reply other threads:[~2013-01-29 18:52 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
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 [this message]
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=20130129.135222.864358079580838703.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Valdis.Kletnieks@vt.edu \
--cc=bhutchings@solarflare.com \
--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).