[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140711135854.GD26045@localhost.localdomain>
Date: Fri, 11 Jul 2014 15:58:56 +0200
From: Frederic Weisbecker <fweisbec@...il.com>
To: Christoph Lameter <cl@...two.org>
Cc: akpm@...ux-foundation.org, Gilad Ben-Yossef <gilad@...yossef.com>,
Thomas Gleixner <tglx@...utronix.de>,
Tejun Heo <tj@...nel.org>, John Stultz <johnstul@...ibm.com>,
Mike Frysinger <vapier@...too.org>,
Minchan Kim <minchan.kim@...il.com>,
Hakan Akkan <hakanakkan@...il.com>,
Max Krasnyansky <maxk@...lcomm.com>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org, hughd@...gle.com,
viresh.kumar@...aro.org, hpa@...or.com, mingo@...nel.org,
peterz@...radead.org
Subject: Re: vmstat: On demand vmstat workers V8
On Fri, Jul 11, 2014 at 08:56:04AM -0500, Christoph Lameter wrote:
> On Fri, 11 Jul 2014, Frederic Weisbecker wrote:
>
> > > @@ -1228,20 +1244,105 @@ static const struct file_operations proc
> > > #ifdef CONFIG_SMP
> > > static DEFINE_PER_CPU(struct delayed_work, vmstat_work);
> > > int sysctl_stat_interval __read_mostly = HZ;
> > > +struct cpumask *cpu_stat_off;
> >
> > I thought you converted it?
>
> Converted what? We still need to keep a cpumask around that tells us which
> processor have vmstat running and which do not.
>
Converted to cpumask_var_t.
I mean we spent dozens emails on that...
--
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