From: Andi Kleen <ak@suse.de>
To: Martin Peschke <mp3@de.ibm.com>
Cc: heiko.carstens@de.ibm.com, clg@fr.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [Patch] statistics infrastructure - update 9
Date: 04 Jul 2006 02:17:25 +0200 [thread overview]
Message-ID: <p73ac7qql4a.fsf@verdi.suse.de> (raw)
In-Reply-To: <1151943862.2936.10.camel@dyn-9-152-230-71.boeblingen.de.ibm.com>
Martin Peschke <mp3@de.ibm.com> writes:
> {
> -#ifdef CONFIG_STATISTICS
> unsigned long flags;
> local_irq_save(flags);
> _statistic_add_as(type, stat, i, value, incr);
> local_irq_restore(flags);
Is there a particular reason you can't use local_t with cpu_local_*?
It would be faster on many architectures than local_irq_save/restore
-Andi
next prev parent reply other threads:[~2006-07-04 0:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 16:24 [Patch] statistics infrastructure - update 9 Martin Peschke
2006-07-03 16:41 ` Cedric Le Goater
2006-07-04 0:17 ` Andi Kleen [this message]
2006-07-06 16:55 ` Martin Peschke
2006-07-06 17:00 ` Andi Kleen
2006-07-10 14:41 ` Martin Peschke
2006-07-04 6:17 ` Heiko Carstens
2006-07-04 7:19 ` Andrew Morton
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=p73ac7qql4a.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=clg@fr.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mp3@de.ibm.com \
/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