Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751805AbaAXIxS (ORCPT ); Fri, 24 Jan 2014 03:53:18 -0500 Received: from mail-oa0-f45.google.com ([209.85.219.45]:62124 "EHLO mail-oa0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751490AbaAXIxO (ORCPT ); Fri, 24 Jan 2014 03:53:14 -0500 MIME-Version: 1.0 In-Reply-To: <20140123140118.GC13345@localhost.localdomain> References: <20140120154058.GA9436@localhost.localdomain> <20140123140118.GC13345@localhost.localdomain> Date: Fri, 24 Jan 2014 14:23:13 +0530 Message-ID: Subject: Re: [QUERY]: Is using CPU hotplug right for isolating CPUs? From: Viresh Kumar To: Frederic Weisbecker Cc: Lei Wen , Kevin Hilman , Lists linaro-kernel , Peter Zijlstra , Linux Kernel Mailing List , Steven Rostedt , Linaro Networking , Tejun Heo Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 23 January 2014 19:31, Frederic Weisbecker wrote: > Ok, so it is fine to migrate the latter kind I guess? Unless somebody has abused the API and used bound workqueues where he should have used unbound ones. > I haven't checked the details but then this quiesce option would involve > a dependency on cpuset for any workload involving workqueues affinity. I'm > not sure we really want this. Besides, workqueues have an existing sysfs interface > that can be easily extended. > > Now indeed we may also want to enforce some policy to make sure that further > created and queued workqueues are affine to a specific subset of CPUs. And then > cpuset sounds like a good idea :) Exactly. Cpuset would be more useful here. Probably we can keep both cpusets and sysfs interface of workqueues.. I will try to add this option under cpuset which will initially move timers and workqueues away from the cpuset in question. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/