summaryrefslogtreecommitdiffstats
path: root/mm/swap_state.c
diff options
context:
space:
mode:
authorIgor Konopko <igor.j.konopko@intel.com>2019-05-04 20:37:53 +0200
committerJens Axboe <axboe@kernel.dk>2019-05-06 10:19:17 -0600
commit6e46b8b24ffbc4ecb5b606094dbc8ed5d6281f59 (patch)
tree4216e3f6367e9162c0b9cf87d01a6ed8dad854c5 /mm/swap_state.c
parent75c89bef6a54943ea0053dc3d27479edfb31b699 (diff)
downloadlinux-6e46b8b24ffbc4ecb5b606094dbc8ed5d6281f59.tar.bz2
lightnvm: pblk: cleanly fail when there is not enough memory
L2P table can be huge in many cases, since it typically requires 1GB of DRAM for 1TB of drive. When there is not enough memory available, OOM killer turns on and kills random processes, which can be very annoying for users. This patch changes the flag for L2P table allocation on order to handle this situation in more user friendly way. GFP_KERNEL and __GPF_HIGHMEM are default flags used in parameterless vmalloc() calls, so they are also keeped in that patch. Additionally __GFP_NOWARN flag is added in order to hide very long dmesg warn in case of the allocation failures. The most important flag introduced in that patch is __GFP_RETRY_MAYFAIL, which would cause allocator to try use free memory and if not available to drop caches, but not to run OOM killer. Signed-off-by: Igor Konopko <igor.j.konopko@intel.com> Reviewed-by: Hans Holmberg <hans.holmberg@cnexlabs.com> Reviewed-by: Javier González <javier@javigon.com> Signed-off-by: Matias Bjørling <mb@lightnvm.io> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'mm/swap_state.c')
0 files changed, 0 insertions, 0 deletions