From: Shaohua Li <shaohua.li@intel.com>
To: Tejun Heo <tj@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"cl@linux.com" <cl@linux.com>,
"eric.dumazet@gmail.com" <eric.dumazet@gmail.com>
Subject: Re: [patch v3 3/3] percpu_counter: use atomic64 for counter in SMP
Date: Mon, 18 Apr 2011 15:43:45 +0800 [thread overview]
Message-ID: <1303112625.3981.191.camel@sli10-conroe> (raw)
In-Reply-To: <20110415041506.GC29512@mtj.dyndns.org>
On Fri, 2011-04-15 at 12:15 +0800, Tejun Heo wrote:
> Hello,
>
> On Thu, Apr 14, 2011 at 10:04:50AM +0800, shaohua.li@intel.com wrote:
> > Index: linux/lib/percpu_counter.c
> > ===================================================================
> > --- linux.orig/lib/percpu_counter.c 2011-04-14 09:53:04.000000000 +0800
> > +++ linux/lib/percpu_counter.c 2011-04-14 10:01:29.000000000 +0800
> > @@ -59,13 +59,17 @@ void percpu_counter_set(struct percpu_co
> > {
> > int cpu;
> >
> > - spin_lock(&fbc->lock);
> > + /*
> > + * Don't really need to disable preempt here, just make sure there is
> > + * no big latency because of preemption
> > + */
> > + preempt_disable();
> > for_each_possible_cpu(cpu) {
> > s32 *pcount = per_cpu_ptr(fbc->counters, cpu);
> > *pcount = 0;
> > }
> > - fbc->count = amount;
> > - spin_unlock(&fbc->lock);
> > + atomic64_set(&fbc->count, amount);
> > + preempt_enable();
>
> Disabling preemption here doesn't make any sense.
> percpu_counter_set() inherently requires its users to guarantee that
> no other user is modifying the percpu counter.
ha, ok.
should I still rebase the patch against Christoph's patch? Looks that
one is still not settled down.
next prev parent reply other threads:[~2011-04-18 7:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 2:04 [patch v3 0/3] percpu_counter: cleanup and fix shaohua.li
2011-04-14 2:04 ` [patch v3 1/3] percpu_counter: change return value and add comments shaohua.li
2011-04-14 2:32 ` Eric Dumazet
2011-04-15 3:41 ` Tejun Heo
2011-04-14 2:04 ` [patch v3 2/3] percpu_counter: fix code for 32bit systems for UP shaohua.li
2011-04-14 2:35 ` Eric Dumazet
2011-04-14 2:44 ` Shaohua Li
2011-04-14 2:54 ` Eric Dumazet
2011-04-18 7:41 ` Shaohua Li
2011-04-14 2:04 ` [patch v3 3/3] percpu_counter: use atomic64 for counter in SMP shaohua.li
2011-04-15 4:15 ` Tejun Heo
2011-04-18 7:43 ` Shaohua Li [this message]
2011-04-18 14:25 ` Christoph Lameter
2011-04-20 1:04 ` Shaohua Li
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=1303112625.3981.191.camel@sli10-conroe \
--to=shaohua.li@intel.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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®