[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170824104247.8288-1-khandual@linux.vnet.ibm.com>
Date: Thu, 24 Aug 2017 16:12:47 +0530
From: Anshuman Khandual <khandual@...ux.vnet.ibm.com>
To: linux-mm@...ck.org, linux-xfs@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: dchinner@...hat.com, bfoster@...hat.com, sandeen@...deen.net
Subject: [PATCH] xfs: Drop setting redundant PF_KSWAPD in kswapd context
xfs_btree_split() calls xfs_btree_split_worker() with args.kswapd set
if current->flags alrady has PF_KSWAPD. Hence we should not again add
PF_KSWAPD into the current flags inside kswapd context. So drop this
redundant flag addition.
Signed-off-by: Anshuman Khandual <khandual@...ux.vnet.ibm.com>
---
fs/xfs/libxfs/xfs_btree.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/xfs/libxfs/xfs_btree.c b/fs/xfs/libxfs/xfs_btree.c
index e0bcc4a..b3c85e3 100644
--- a/fs/xfs/libxfs/xfs_btree.c
+++ b/fs/xfs/libxfs/xfs_btree.c
@@ -2895,7 +2895,7 @@ struct xfs_btree_split_args {
* in any way.
*/
if (args->kswapd)
- new_pflags |= PF_MEMALLOC | PF_SWAPWRITE | PF_KSWAPD;
+ new_pflags |= PF_MEMALLOC | PF_SWAPWRITE;
current_set_flags_nested(&pflags, new_pflags);
--
1.8.5.2
Powered by blists - more mailing lists