[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1312547447.18583.195.camel@gandalf.stny.rr.com>
Date: Fri, 05 Aug 2011 08:30:47 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Yong Zhang <yong.zhang0@...il.com>
Cc: LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Mike Galbraith <mgalbraith@...e.de>,
"Luis Claudio R." Gon�alves
<lgoncalv@...hat.com>,
Matthew Hank Sabins <msabins@...ux.vnet.ibm.com>,
Gregory Haskins <gregory.haskins@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH][GIT PULL] sched/cpupri: Remove the vec->lock
On Fri, 2011-08-05 at 16:20 +0800, Yong Zhang wrote:
> On Tue, Aug 02, 2011 at 04:36:12PM -0400, Steven Rostedt wrote:
> > diff --git a/kernel/sched_cpupri.h b/kernel/sched_cpupri.h
> > index 9fc7d38..6b4cd17 100644
> > --- a/kernel/sched_cpupri.h
> > +++ b/kernel/sched_cpupri.h
> > @@ -12,9 +12,8 @@
> > /* values 2-101 are RT priorities 0-99 */
> >
> > struct cpupri_vec {
> > - raw_spinlock_t lock;
> > - int count;
> > - cpumask_var_t mask;
> > + atomic_t count;
> > + cpumask_var_t mask;
> > };
> >
> > struct cpupri {
>
> So cpupri->pri_active and macro CPUPRI_NR_PRI_WORDS is not needed any more?
It doesn't appear so. Looks like they can be removed too.
Want to send a patch?
Thanks!
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists