From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Dave Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: [patch 2/3] tcp: use read mostly for CUBIC parameters
Date: Mon, 12 Feb 2007 08:03:19 -0800 [thread overview]
Message-ID: <20070212160336.527416565@linux-foundation.org> (raw)
In-Reply-To: 20070212160317.545906075@linux-foundation.org
[-- Attachment #1: bic-mostly.patch --]
[-- Type: text/plain, Size: 1342 bytes --]
These module parameters should be in the read mostly area
to avoid cache pollution.
Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org>
---
net/ipv4/tcp_cubic.c | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
--- tcp.orig/net/ipv4/tcp_cubic.c 2007-02-12 07:28:55.000000000 -0800
+++ tcp/net/ipv4/tcp_cubic.c 2007-02-12 07:32:33.000000000 -0800
@@ -26,16 +26,16 @@
*/
#define BICTCP_HZ 10 /* BIC HZ 2^10 = 1024 */
-static int fast_convergence = 1;
-static int max_increment = 16;
-static int beta = 819; /* = 819/1024 (BICTCP_BETA_SCALE) */
-static int initial_ssthresh = 100;
-static int bic_scale = 41;
-static int tcp_friendliness = 1;
-
-static u32 cube_rtt_scale;
-static u32 beta_scale;
-static u64 cube_factor;
+static int fast_convergence __read_mostly = 1;
+static int max_increment __read_mostly = 16;
+static int beta __read_mostly = 819; /* = 819/1024 (BICTCP_BETA_SCALE) */
+static int initial_ssthresh __read_mostly = 100;
+static int bic_scale __read_mostly = 41;
+static int tcp_friendliness __read_mostly = 1;
+
+static u32 cube_rtt_scale __read_mostly;
+static u32 beta_scale __read_mostly;
+static u64 cube_factor __read_mostly;
/* Note parameters that are used for precomputing scale factors are read-only */
module_param(fast_convergence, int, 0644);
--
next prev parent reply other threads:[~2007-02-12 16:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-12 16:03 [patch 0/3] TCP trivial patches Stephen Hemminger
2007-02-12 16:03 ` [patch 1/3] tcp: cleanup of htcp Stephen Hemminger
2007-02-12 21:14 ` David Miller
2007-02-12 21:28 ` [patch 1/3] tcp: cleanup of htcp (resend) Stephen Hemminger
2007-02-12 21:34 ` David Miller
2007-02-12 16:03 ` Stephen Hemminger [this message]
2007-02-12 21:15 ` [patch 2/3] tcp: use read mostly for CUBIC parameters David Miller
2007-02-12 16:03 ` [patch 3/3] tcp: remove experimental variants from default list Stephen Hemminger
2007-02-12 19:11 ` Baruch Even
2007-02-12 20:13 ` Ian McDonald
2007-02-12 20:26 ` Stephen Hemminger
2007-02-12 20:34 ` David Miller
2007-02-12 20:32 ` David Miller
2007-02-12 20:37 ` Stephen Hemminger
2007-02-12 20:47 ` David Miller
2007-02-12 21:05 ` Ian McDonald
2007-02-12 20:20 ` David Miller
2007-02-12 22:12 ` Baruch Even
2007-02-12 22:53 ` David Miller
2007-02-13 9:56 ` Baruch Even
2007-02-13 16:49 ` SANGTAE HA
2007-02-13 17:42 ` Baruch Even
2007-02-13 19:54 ` John Heffner
2007-02-13 20:06 ` David Miller
2007-02-13 20:23 ` Stephen Hemminger
2007-02-13 17:41 ` Injong Rhee
2007-02-13 18:23 ` Baruch Even
2007-02-13 19:56 ` David Miller
2007-02-13 20:06 ` Baruch Even
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=20070212160336.527416565@linux-foundation.org \
--to=shemminger@linux-foundation.org \
--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).