From: Eric Dumazet <eric.dumazet@gmail.com>
To: Christoph Lameter <cl@linux.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] percpu_counter: change inaccurate comment
Date: Thu, 07 Oct 2010 22:04:20 +0200 [thread overview]
Message-ID: <1286481860.3745.30.camel@edumazet-laptop> (raw)
In-Reply-To: <alpine.DEB.2.00.1010071440220.28032@router.home>
Le jeudi 07 octobre 2010 à 14:42 -0500, Christoph Lameter a écrit :
> On Thu, 7 Oct 2010, Eric Dumazet wrote:
>
> > percpu_counter used to be huge objects, they are not anymore,
> > thanks to fine alloc_percpu() granularity.
> >
> > We now consume 4 bytes per possible cpu.
>
> Ahh I did not notice that they switched.... Then we may also want the
> following patch to improve performance. It would even be better if we
> could do a this_cpu_add(fbc->counters, amount) there but the 64 bit size
> fo count looks suspiciously like you are expecting overflows beyond ints
> max size.
>
Yes, this 64bit interface is very strange.
>
> Subject: percpu_counter: Use this_cpu_ptr instead of per_cpu_ptr
>
> this_cpu_ptr avoids an array lookup and can use the percpu
> offset of the local cpu directly.
>
> Signed-off-by: Christoph Lameter <cl@linux.com>
>
> ---
> lib/percpu_counter.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> Index: linux-2.6/lib/percpu_counter.c
> ===================================================================
> --- linux-2.6.orig/lib/percpu_counter.c 2010-10-07 14:36:39.000000000 -0500
> +++ linux-2.6/lib/percpu_counter.c 2010-10-07 14:38:43.000000000 -0500
> @@ -30,9 +30,9 @@ void __percpu_counter_add(struct percpu_
> {
> s64 count;
> s32 *pcount;
> - int cpu = get_cpu();
>
> - pcount = per_cpu_ptr(fbc->counters, cpu);
> + preempt_disable();
> + pcount = this_cpu_ptr(fbc->counters);
> count = *pcount + amount;
> if (count >= batch || count <= -batch) {
> spin_lock(&fbc->lock);
> @@ -42,7 +42,7 @@ void __percpu_counter_add(struct percpu_
> } else {
> *pcount = count;
> }
> - put_cpu();
> + preempt_enable();
> }
> EXPORT_SYMBOL(__percpu_counter_add);
>
If enclosed by preempt_disable()/preempt_enable(), maybe we could use
__this_cpu_ptr() ?
next prev parent reply other threads:[~2010-10-07 20:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 16:37 Eric Dumazet
2010-10-07 19:42 ` Christoph Lameter
2010-10-07 20:04 ` Eric Dumazet [this message]
2010-10-07 20:13 ` Christoph Lameter
2010-10-07 20:42 ` Eric Dumazet
2010-10-07 21:06 ` Christoph Lameter
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=1286481860.3745.30.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®