mirror of
https://github.com/torvalds/linux.git
synced 2024-11-26 22:21:42 +00:00
73d03931be
As Christoph said [1], "vm_map_ram is supposed to generally behave better. So if it doesn't please report that that to the arch maintainer and linux-mm so that they can look into the issue. Having user make choices of deep down kernel internals is just a horrible interface. Please talk to maintainers of other bits of the kernel if you see issues and / or need enhancements. " Let's redo the previous conclusion and kill the vmap approach. [1] https://lore.kernel.org/r/20190830165533.GA10909@infradead.org/ Reported-by: Christoph Hellwig <hch@infradead.org> Signed-off-by: Gao Xiang <gaoxiang25@huawei.com> Link: https://lore.kernel.org/r/20190904020912.63925-21-gaoxiang25@huawei.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
||
---|---|---|
.. | ||
compress.h | ||
data.c | ||
decompressor.c | ||
dir.c | ||
erofs_fs.h | ||
inode.c | ||
internal.h | ||
Kconfig | ||
Makefile | ||
namei.c | ||
super.c | ||
tagptr.h | ||
utils.c | ||
xattr.c | ||
xattr.h | ||
zdata.c | ||
zdata.h | ||
zmap.c | ||
zpvec.h |