diff options
author | Oscar Salvador <osalvador@suse.de> | 2018-08-21 21:54:06 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2018-08-22 10:52:45 -0700 |
commit | 5df66d306ec9b1952d3d183fe4e2ced1a7b2bddb (patch) | |
tree | 5e5bac679ccbeaff5e73970e6ae536738ae5db32 /fs/proc/inode.c | |
parent | c8bd134a4bddafe5917d163eea73873932c15e83 (diff) | |
download | linux-stable-5df66d306ec9b1952d3d183fe4e2ced1a7b2bddb.tar.gz linux-stable-5df66d306ec9b1952d3d183fe4e2ced1a7b2bddb.tar.bz2 linux-stable-5df66d306ec9b1952d3d183fe4e2ced1a7b2bddb.zip |
mm: fix comment for NODEMASK_ALLOC
Currently, NODEMASK_ALLOC allocates a nodemask_t with kmalloc when
NODES_SHIFT is higher than 8, otherwise it declares it within the stack.
The comment says that the reasoning behind this, is that nodemask_t will
be 256 bytes when NODES_SHIFT is higher than 8, but this is not true. For
example, NODES_SHIFT = 9 will give us a 64 bytes nodemask_t. Let us fix
up the comment for that.
Another thing is that it might make sense to let values lower than
128bytes be allocated in the stack. Although this all depends on the
depth of the stack (and this changes from function to function), I think
that 64 bytes is something we can easily afford. So we could even bump
the limit by 1 (from > 8 to > 9).
Link: http://lkml.kernel.org/r/20180820085516.9687-1-osalvador@techadventures.net
Signed-off-by: Oscar Salvador <osalvador@suse.de>
Reviewed-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/proc/inode.c')
0 files changed, 0 insertions, 0 deletions