diff options
author | Vladimir Davydov <vdavydov@parallels.com> | 2014-10-20 15:50:30 +0400 |
---|---|---|
committer | Tejun Heo <tj@kernel.org> | 2014-10-27 11:15:27 -0400 |
commit | 344736f29b359790facd0b7a521e367f1715c11c (patch) | |
tree | c32487de22e7640a828f28819b5707790ede5105 /Makefile | |
parent | 8447a0fee974433f7e0035fd30e1edecf00e014f (diff) | |
download | linux-stable-344736f29b359790facd0b7a521e367f1715c11c.tar.gz linux-stable-344736f29b359790facd0b7a521e367f1715c11c.tar.bz2 linux-stable-344736f29b359790facd0b7a521e367f1715c11c.zip |
cpuset: simplify cpuset_node_allowed API
Current cpuset API for checking if a zone/node is allowed to allocate
from looks rather awkward. We have hardwall and softwall versions of
cpuset_node_allowed with the softwall version doing literally the same
as the hardwall version if __GFP_HARDWALL is passed to it in gfp flags.
If it isn't, the softwall version may check the given node against the
enclosing hardwall cpuset, which it needs to take the callback lock to
do.
Such a distinction was introduced by commit 02a0e53d8227 ("cpuset:
rework cpuset_zone_allowed api"). Before, we had the only version with
the __GFP_HARDWALL flag determining its behavior. The purpose of the
commit was to avoid sleep-in-atomic bugs when someone would mistakenly
call the function without the __GFP_HARDWALL flag for an atomic
allocation. The suffixes introduced were intended to make the callers
think before using the function.
However, since the callback lock was converted from mutex to spinlock by
the previous patch, the softwall check function cannot sleep, and these
precautions are no longer necessary.
So let's simplify the API back to the single check.
Suggested-by: David Rientjes <rientjes@google.com>
Signed-off-by: Vladimir Davydov <vdavydov@parallels.com>
Acked-by: Christoph Lameter <cl@linux.com>
Acked-by: Zefan Li <lizefan@huawei.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions