From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Optimize multi-CPU tlb flushing a little more
Date: Mon, 13 Feb 2012 16:23:59 +0000 [thread overview]
Message-ID: <20120213162359.GC25655@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAH+eYFC_mkdObV0NfN5Jtv0L6fM9e0YGOBghTEVSqf=TAFxdXw@mail.gmail.com>
On Mon, Feb 13, 2012 at 09:36:35PM +0530, Rabin Vincent wrote:
> This part conditionally calls get_cpu() but unconditionally calls
> put_cpu():
Can you try getting rid of put_cpu(), and replacing get_cpu()
with smp_processor_id().
In theory, this function should be called with preempt disabled so
smp_processor_id() should be safe here.
Thanks.
next prev parent reply other threads:[~2012-02-13 16:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 11:06 [PATCH] Optimize multi-CPU tlb flushing a little more Russell King - ARM Linux
2011-09-06 16:53 ` Catalin Marinas
2012-02-13 16:06 ` Rabin Vincent
2012-02-13 16:23 ` Russell King - ARM Linux [this message]
2012-02-13 16:59 ` Rabin Vincent
2012-02-14 21:59 ` Stephen Warren
2012-02-14 22:23 ` Russell King - ARM Linux
2012-02-14 22:38 ` Stephen Warren
2012-02-14 23:21 ` Stephen Warren
2012-02-14 23:34 ` Russell King - ARM Linux
2012-02-15 0:01 ` Stephen Warren
2012-02-14 18:52 ` Stephen Warren
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=20120213162359.GC25655@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).