Main-line Linux kernel tree http://www.kernel.org
Go to file
Xianting Tian 576e85c5e9 blk-mq: remove the calling of local_memory_node()
We don't need to check whether the node is memoryless numa node before
calling allocator interface. SLUB(and SLAB,SLOB) relies on the page
allocator to pick a node. Page allocator should deal with memoryless
nodes just fine. It has zonelists constructed for each possible nodes.
And it will automatically fall back into a node which is closest to the
requested node. As long as __GFP_THISNODE is not enforced of course.

The code comments of kmem_cache_alloc_node() of SLAB also showed this:
 * Fallback to other node is possible if __GFP_THISNODE is not set.

blk-mq code doesn't set __GFP_THISNODE, so we can remove the calling
of local_memory_node().

Signed-off-by: Xianting Tian <tian.xianting@h3c.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
2020-10-20 07:08:17 -06:00
arch * Use XORL instead of XORQ to avoid a REX prefix and save some bytes in 2020-10-13 13:36:07 -07:00
block blk-mq: remove the calling of local_memory_node() 2020-10-20 07:08:17 -06:00
certs
crypto drivers-5.10-2020-10-12 2020-10-13 13:04:41 -07:00
Documentation block: add zone specific block statuses 2020-10-13 15:05:05 -06:00
drivers zram: Fix __zram_bvec_{read,write}() locking order 2020-10-19 09:32:28 -06:00
fs io_uring-5.10-2020-10-12 2020-10-13 12:36:21 -07:00
include block: add zone specific block statuses 2020-10-13 15:05:05 -06:00
init io_uring-5.10-2020-10-12 2020-10-13 12:36:21 -07:00
ipc
kernel io_uring-5.10-2020-10-12 2020-10-13 12:36:21 -07:00
lib sgl_alloc_order: fix memory leak 2020-10-16 09:31:09 -06:00
LICENSES
mm
net io_uring-5.10-2020-10-12 2020-10-13 12:36:21 -07:00
samples
scripts
security
sound
tools
usr
virt
.clang-format
.cocciconfig
.get_maintainer.ignore
.gitattributes
.gitignore
.mailmap
COPYING
CREDITS
Kbuild
Kconfig
MAINTAINERS libata-5.10-2020-10-12 2020-10-13 12:50:48 -07:00
Makefile
README

Linux kernel
============

There are several guides for kernel developers and users. These guides can
be rendered in a number of formats, like HTML and PDF. Please read
Documentation/admin-guide/README.rst first.

In order to build the documentation, use ``make htmldocs`` or
``make pdfdocs``.  The formatted documentation can also be read online at:

    https://www.kernel.org/doc/html/latest/

There are various text files in the Documentation/ subdirectory,
several of them using the Restructured Text markup notation.

Please read the Documentation/process/changes.rst file, as it contains the
requirements for building and running the kernel, and information about
the problems which may result by upgrading your kernel.