[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohpokbb3ko3sW4kuDKZSoY1qJ6apVVR3-jpv=7m5ZX__YP8Q@mail.gmail.com>
Date: Mon, 20 Jan 2014 20:30:10 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Lei Wen <adrian.wenl@...il.com>
Cc: Frédéric Weisbecker <fweisbec@...il.com>,
Kevin Hilman <khilman@...aro.org>,
Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
Peter Zijlstra <peterz@...radead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Linaro Networking <linaro-networking@...aro.org>
Subject: Re: [QUERY]: Is using CPU hotplug right for isolating CPUs?
On 20 January 2014 19:29, Lei Wen <adrian.wenl@...il.com> wrote:
> Hi Viresh,
Hi Lei,
> I have one question regarding unbounded workqueue migration in your case.
> You use hotplug to migrate the unbounded work to other cpus, but its cpu mask
> would still be 0xf, since cannot be changed by cpuset.
>
> My question is how you could prevent this unbounded work migrate back
> to your isolated cpu?
> Seems to me there is no such mechanism in kernel, am I understand wrong?
These workqueues are normally queued back from workqueue handler. And we
normally queue them on the local cpu, that's the default behavior of workqueue
subsystem. And so they land up on the same CPU again and again.
--
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