linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Alexander Monakov <amonakov@gmail.com>
Cc: Konstantin Khlebnikov <koct9i@gmail.com>,
	linux-acpi@vger.kernel.org,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-kernel@vger.kernel.org, Len Brown <lenb@kernel.org>,
	Tom Boshoven <tomboshoven@gmail.com>,
	x86@kernel.org, Josh Triplett <josh@joshtriplett.org>
Subject: Re: [PATCH] ACPI/osl: speedup grace period in acpi_os_map_cleanup
Date: Sat, 8 Nov 2014 16:51:24 -0800	[thread overview]
Message-ID: <20141109005124.GG4901@linux.vnet.ibm.com> (raw)
In-Reply-To: <CABtfrpDryV5XEzBOttTuGZ7Tvyy4QUo1pajvO07=6tpozjVLzQ@mail.gmail.com>

On Sun, Nov 09, 2014 at 03:24:34AM +0400, Alexander Monakov wrote:
> On Sun, Nov 9, 2014 at 1:13 AM, Paul E. McKenney
> <paulmck@linux.vnet.ibm.com> wrote:
> >
> > Did anyone try replacing the synchronize_rcu() with
> > synchronize_rcu_expedited()?  That should provide substantial speedups
> > over synchronize_rcu().
> 
> I've just briefly tested it on my laptop, and it also helps to avoid the issue.

OK, good.

In the past, synchronize_rcu_expedited() has been a bit unfriendly to
battery-powered platforms and to real-time and HPC workloads, but
recent changes for the most part fix this.

							Thanx, Paul


  reply	other threads:[~2014-11-09  0:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-08  8:47 [PATCH] ACPI/osl: speedup grace period in acpi_os_map_cleanup Konstantin Khlebnikov
2014-11-08 22:13 ` Paul E. McKenney
2014-11-08 23:24   ` Alexander Monakov
2014-11-09  0:51     ` Paul E. McKenney [this message]
2014-11-09 11:04       ` Konstantin Khlebnikov
2014-11-09  9:53 ` [PATCH v2] " Konstantin Khlebnikov
2014-11-09 22:00   ` Paul E. McKenney
2014-11-14 22:48     ` Rafael J. Wysocki
2014-11-14 15:52   ` joeyli

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=20141109005124.GG4901@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=amonakov@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=koct9i@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=tomboshoven@gmail.com \
    --cc=x86@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).