[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0BA3FCBA62E2DC44AF3030971E174FB32EA8768F@hasmsx107.ger.corp.intel.com>
Date: Wed, 23 Mar 2016 08:33:41 +0000
From: "Grumbach, Emmanuel" <emmanuel.grumbach@...el.com>
To: Eva Rachel Retuya <eraretuya@...il.com>,
"outreachy-kernel@...glegroups.com"
<outreachy-kernel@...glegroups.com>
CC: "Berg, Johannes" <johannes.berg@...el.com>,
linuxwifi <linuxwifi@...el.com>,
"kvalo@...eaurora.org" <kvalo@...eaurora.org>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"tj@...nel.org" <tj@...nel.org>
Subject: Re: [PATCH v3] iwlwifi: dvm: use alloc_ordered_workqueue()
On 03/19/2016 07:15 AM, Eva Rachel Retuya wrote:
> Use alloc_ordered_workqueue() to allocate the workqueue instead of
> create_singlethread_workqueue() since the latter is deprecated and is scheduled
> for removal.
>
> There are work items doing related operations that shouldn't be swapped when
> queued in a certain order hence preserve the strict execution ordering of a
> single threaded (ST) workqueue by switching to alloc_ordered_workqueue().
>
> WQ_MEM_RECLAIM flag is not needed since the worker is not depended
> during memory reclaim.
>
> Signed-off-by: Eva Rachel Retuya <eraretuya@...il.com>
> Acked-by: Tejun Heo <tj@...nel.org>
> ---
Applied - thanks.
Powered by blists - more mailing lists