From: Daniel J Blueman <daniel@numascale.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Steffen Persvold <sp@numascale.com>, LKML <linux-kernel@vger.kernel.org>
Subject: RCU fanout leaf balancing
Date: Sat, 25 Oct 2014 14:59:24 +0800 [thread overview]
Message-ID: <544B4A4C.5070807@numascale.com> (raw)
Hi Paul,
Finding earlier reference to increasing RCU fanout leaf for the purpose
of "decrease[ing] cache-miss overhead for large systems", would your
suggestion be to increase the value to the next hierarchy core-count
above 16?
If we have say 32 interconnected 48-core servers; 3 sockets of dual-node
8-core Opteron 6300s, so 1536 cores in all. Latency across the coherent
interconnect is O(100x) higher than the internal Hypertransport
interconnect, so if we set RCU_FANOUT_LEAF to 48 to keep leaf-checking
local to one Hypertransport fabric, what wisdom would one use for
RCU_FANOUT? 4x leaf?
Or, would it be more cache-friendly to set RCU_FANOUT_LEAF to 8 and
RCU_FANOUT to 48?
Many thanks,
Daniel
--
Daniel J Blueman
Principal Software Engineer, Numascale
next reply other threads:[~2014-10-25 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 6:59 Daniel J Blueman [this message]
2014-10-25 13:48 ` RCU fanout leaf balancing Paul E. McKenney
2014-10-27 1:08 ` Daniel J Blueman
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=544B4A4C.5070807@numascale.com \
--to=daniel@numascale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sp@numascale.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.