All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org, hpa@zytor.com,
	paulmck@linux.vnet.ibm.com, akpm@linux-foundation.org,
	khilman@linaro.org, tglx@linutronix.de, axboe@fb.com,
	linux-tip-commits@vger.kernel.org
Subject: Re: [tip:timers/nohz] nohz: Move full nohz kick to its own IPI
Date: Mon, 5 May 2014 17:06:01 +0200	[thread overview]
Message-ID: <20140505150558.GC2099@localhost.localdomain> (raw)
In-Reply-To: <20140505145815.GQ26782@laptop.programming.kicks-ass.net>

On Mon, May 05, 2014 at 04:58:15PM +0200, Peter Zijlstra wrote:
> On Mon, May 05, 2014 at 04:52:59PM +0200, Frederic Weisbecker wrote:
> > > Should we instead do irq_work_queue_on() ?
> > 
> > I would really much prefer that yeah. But if we do that, expect some added overhead on the local
> > irq_work_queue() path though. irq_work_raise can't use local cmpxchg ops anymore.
> > 
> > Or we can have a different pending raise system for remote irq work.
> > 
> > I can try something.
> 
> Loosing that local cmpxchg shouldn't be a problem, I don't  thnk this is
> a particularly hot path.

Then the conversion is easy since most of the irq work code should
already work for remote queuing.

I'll come up with a patch soon.

Thanks.

      reply	other threads:[~2014-05-05 15:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tip-72aacf0259bb7d53b7a3b5b2f7bf982acaa52b61@git.kernel.org>
2014-05-05 12:37 ` [tip:timers/nohz] nohz: Move full nohz kick to its own IPI Peter Zijlstra
2014-05-05 13:31   ` Peter Zijlstra
2014-05-05 15:04     ` Frederic Weisbecker
2014-05-05 15:12       ` Peter Zijlstra
2014-05-05 15:34         ` Frederic Weisbecker
2014-05-07 15:17           ` Peter Zijlstra
2014-05-07 15:29             ` Frederic Weisbecker
2014-05-07 15:37               ` Peter Zijlstra
2014-05-07 16:05                 ` Frederic Weisbecker
2014-05-07 16:13                   ` Peter Zijlstra
2014-05-07 19:07                     ` Ingo Molnar
2014-05-09 15:10                       ` Frederic Weisbecker
2014-05-11  5:34                         ` Ingo Molnar
2014-05-05 14:52   ` Frederic Weisbecker
2014-05-05 14:58     ` Peter Zijlstra
2014-05-05 15:06       ` Frederic Weisbecker [this message]

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=20140505150558.GC2099@localhost.localdomain \
    --to=fweisbec@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@fb.com \
    --cc=hpa@zytor.com \
    --cc=khilman@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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.