Re: [PATCH v2 08/10] cpuset: allow to keep tasks in empty cpusets

Hey, On Thu, Jun 06, 2013 at 06:26:46PM +0800, Li Zefan wrote: > > I wonder whether it'd be possible to merge the two paths. My > > suspicion is that we probably don't need propagate_hotplug_work > > anymore now that we can drop RCU read lock while doing the pre-order > > walk. What do you think

Re: [PATCH v2 08/10] cpuset: allow to keep tasks in empty cpusets

On 2013/6/6 4:51, Tejun Heo wrote: > Hello, Li. > > On Wed, Jun 05, 2013 at 05:16:59PM +0800, Li Zefan wrote: >> @@ -2092,11 +2183,13 @@ static void cpuset_propagate_hotplug_workfn(struct >> work_struct *work) >> mutex_unlock(&cpuset_mutex); >> >> /* >> - * If @cs became empty, mo

Re: [PATCH v2 08/10] cpuset: allow to keep tasks in empty cpusets

Hello, Li. On Wed, Jun 05, 2013 at 05:16:59PM +0800, Li Zefan wrote: > @@ -2092,11 +2183,13 @@ static void cpuset_propagate_hotplug_workfn(struct > work_struct *work) > mutex_unlock(&cpuset_mutex); > > /* > - * If @cs became empty, move tasks to the nearest ancestor with > -