diff options
author | Kevin Hao <haokexin@gmail.com> | 2021-02-04 18:56:35 +0800 |
---|---|---|
committer | Jakub Kicinski <kuba@kernel.org> | 2021-02-06 11:57:28 -0800 |
commit | b358e2122b9d7aa99f681d4edfafd999845d16ff (patch) | |
tree | 2bb2a9ee6ed3e4766ba90da3da0b8c521fbfe94d /include/linux/skbuff.h | |
parent | a455fcd7c77046d576dcfe41c1361928dd8b5eaf (diff) | |
download | linux-stable-b358e2122b9d7aa99f681d4edfafd999845d16ff.tar.gz linux-stable-b358e2122b9d7aa99f681d4edfafd999845d16ff.tar.bz2 linux-stable-b358e2122b9d7aa99f681d4edfafd999845d16ff.zip |
mm: page_frag: Introduce page_frag_alloc_align()
In the current implementation of page_frag_alloc(), it doesn't have
any align guarantee for the returned buffer address. But for some
hardwares they do require the DMA buffer to be aligned correctly,
so we would have to use some workarounds like below if the buffers
allocated by the page_frag_alloc() are used by these hardwares for
DMA.
buf = page_frag_alloc(really_needed_size + align);
buf = PTR_ALIGN(buf, align);
These codes seems ugly and would waste a lot of memories if the buffers
are used in a network driver for the TX/RX. So introduce
page_frag_alloc_align() to make sure that an aligned buffer address is
returned.
Signed-off-by: Kevin Hao <haokexin@gmail.com>
Acked-by: Vlastimil Babka <vbabka@suse.cz>
Reviewed-by: Alexander Duyck <alexanderduyck@fb.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'include/linux/skbuff.h')
0 files changed, 0 insertions, 0 deletions