On Fri, Aug 01, 2014 at 01:16:05PM -0400, Chris Metcalf wrote:
> On 7/31/2014 9:39 PM, Lai Jiangshan wrote:
> >On 08/01/2014 12:09 AM, Chris Metcalf wrote:
> >>On 7/31/2014 7:51 AM, Michal Hocko wrote:
> >>>On Thu 31-07-14 11:30:19, Lai Jiangshan wrote:
> It is suggested that cpumask_var_t and
On 7/31/2014 9:39 PM, Lai Jiangshan wrote:
On 08/01/2014 12:09 AM, Chris Metcalf wrote:
On 7/31/2014 7:51 AM, Michal Hocko wrote:
On Thu 31-07-14 11:30:19, Lai Jiangshan wrote:
It is suggested that cpumask_var_t and alloc_cpumask_var() should be used
instead of struct cpumask. But I don't wan
On 08/01/2014 12:09 AM, Chris Metcalf wrote:
> On 7/31/2014 7:51 AM, Michal Hocko wrote:
>> On Thu 31-07-14 11:30:19, Lai Jiangshan wrote:
>>> It is suggested that cpumask_var_t and alloc_cpumask_var() should be used
>>> instead of struct cpumask. But I don't want to add this complicity nor
>>> le
On 7/31/2014 7:51 AM, Michal Hocko wrote:
On Thu 31-07-14 11:30:19, Lai Jiangshan wrote:
It is suggested that cpumask_var_t and alloc_cpumask_var() should be used
instead of struct cpumask. But I don't want to add this complicity nor
leave this unwelcome "static struct cpumask has_work;", so I
On Thu 31-07-14 11:30:19, Lai Jiangshan wrote:
> It is suggested that cpumask_var_t and alloc_cpumask_var() should be used
> instead of struct cpumask. But I don't want to add this complicity nor
> leave this unwelcome "static struct cpumask has_work;", so I just remove
> it and use flush_work() t
It is suggested that cpumask_var_t and alloc_cpumask_var() should be used
instead of struct cpumask. But I don't want to add this complicity nor
leave this unwelcome "static struct cpumask has_work;", so I just remove
it and use flush_work() to perform on all online drain_work. flush_work()
perfo
6 matches
Mail list logo