[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <960cff8a55c83c0d8846306c1b286ec545e9e5f4.1473002371.git.bhaktipriya96@gmail.com>
Date: Sun, 4 Sep 2016 20:52:39 +0530
From: Bhaktipriya Shridhar <bhaktipriya96@...il.com>
To: David Howells <dhowells@...hat.com>
Cc: linux-kernel@...r.kernel.org, linux-afs@...ts.infradead.org,
Tejun Heo <tj@...nel.org>
Subject: [PATCH v3 1/4] fs/afs/vlocation: Remove deprecated
create_singlethread_workqueue
The workqueue "afs_vlocation_update_worker" queues a single work item
&afs_vlocation_update and hence it doesn't require execution ordering.
Hence, alloc_workqueue has been used to replace the deprecated
create_singlethread_workqueue instance.
Since the workqueue is being used on a memory reclaim path, WQ_MEM_RECLAIM
flag has been set to ensure forward progress under memory pressure.
Since there are fixed number of work items, explicit concurrency
limit is unnecessary here.
Signed-off-by: Bhaktipriya Shridhar <bhaktipriya96@...il.com>
---
Changes in v3:
- No change
fs/afs/vlocation.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/afs/vlocation.c b/fs/afs/vlocation.c
index 5297678..45a8639 100644
--- a/fs/afs/vlocation.c
+++ b/fs/afs/vlocation.c
@@ -594,8 +594,8 @@ static void afs_vlocation_reaper(struct work_struct *work)
*/
int __init afs_vlocation_update_init(void)
{
- afs_vlocation_update_worker =
- create_singlethread_workqueue("kafs_vlupdated");
+ afs_vlocation_update_worker = alloc_workqueue("kafs_vlupdated",
+ WQ_MEM_RECLAIM, 0);
return afs_vlocation_update_worker ? 0 : -ENOMEM;
}
--
2.1.4
Powered by blists - more mailing lists