netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: edumazet@google.com, davem@davemloft.net, brouer@redhat.com
Cc: netdev@vger.kernel.org
Subject: Measurable performance improvements from RCU_INIT_POINTER()?
Date: Sat, 19 Jul 2014 01:12:40 -0700	[thread overview]
Message-ID: <20140719081240.GA13806@linux.vnet.ibm.com> (raw)

Hello!

Did the replacement of selected calls to rcu_assign_pointer() by
RCU_INIT_POINTER() in the networking stack result in measurable
system-level performance improvements?

The reason I ask is that some of the compiler guys on the C and C++
standards committees are suggesting changes that would add barriers
in some cases.  I suspect that this is a very bad idea, and was hoping
that you guys would have some hard numbers on the system-level effects
of barriers.  ;-)

							Thanx, Paul

                 reply	other threads:[~2014-07-19 17:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140719081240.GA13806@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=brouer@redhat.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --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).