public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Anton Blanchard <anton@samba.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	miltonm@bga.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] generic-ipi: Use DEFINE_PER_CPU_SHARED_ALIGNED for IPI data
Date: Mon, 18 Jan 2010 08:27:01 +0100	[thread overview]
Message-ID: <20100118072700.GC13771@kernel.dk> (raw)
In-Reply-To: <20100118020051.GR12666@kryten>

On Mon, Jan 18 2010, Anton Blanchard wrote:
> From: Milton Miller <miltonm@bga.com>
> 
> The smp ipi data is passed around and given write access by other cpus
> and should be seperated from per-cpu data consumed by this cpu.
> 
> Looking for hot lines, I saw call_function_data shared with tick_cpu_sched.

Looks good to me.

Acked-by: Jens Axboe <jens.axboe@oracle.com>

-- 
Jens Axboe


  reply	other threads:[~2010-01-18  7:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-18  2:00 [PATCH] generic-ipi: Use DEFINE_PER_CPU_SHARED_ALIGNED for IPI data Anton Blanchard
2010-01-18  7:27 ` Jens Axboe [this message]
2010-01-19 14:22 ` [tip:core/ipi] generic-ipi: Optimize accesses by using " tip-bot for Milton Miller

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=20100118072700.GC13771@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=anton@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miltonm@bga.com \
    --cc=mingo@elte.hu \
    /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