[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <95fb201c-1623-149b-a72e-ed4860f742e1@iogearbox.net>
Date: Wed, 21 Aug 2019 14:35:19 +0200
From: Daniel Borkmann <daniel@...earbox.net>
To: Ivan Khoronzhuk <ivan.khoronzhuk@...aro.org>,
magnus.karlsson@...el.com, bjorn.topel@...el.com
Cc: davem@...emloft.net, hawk@...nel.org, john.fastabend@...il.com,
jakub.kicinski@...ronome.com, netdev@...r.kernel.org,
bpf@...r.kernel.org, xdp-newbies@...r.kernel.org,
linux-kernel@...r.kernel.org, jlemon@...gsvamp.com, yhs@...com,
andrii.nakryiko@...il.com
Subject: Re: [PATCH bpf-next v2 0/3] xdpsock: allow mmap2 usage for 32bits
On 8/15/19 2:13 PM, Ivan Khoronzhuk wrote:
> This patchset contains several improvements for af_xdp socket umem
> mappings for 32bit systems. Also, there is one more patch outside of
> this series that on linux-next tree and related to mmap2 af_xdp umem
> offsets: "mm: mmap: increase sockets maximum memory size pgoff for 32bits"
> https://lkml.org/lkml/2019/8/12/549
>
> Based on bpf-next/master
>
> Prev: https://lkml.org/lkml/2019/8/13/437
>
> v2..v1:
> - replaced "libbpf: add asm/unistd.h to xsk to get __NR_mmap2" on
> "libbpf: use LFS (_FILE_OFFSET_BITS) instead of direct mmap2
> syscall"
> - use vmap along with page_address to avoid overkill
> - define mmap syscall trace5 for mmap if defined
>
> Ivan Khoronzhuk (3):
> libbpf: use LFS (_FILE_OFFSET_BITS) instead of direct mmap2 syscall
> xdp: xdp_umem: replace kmap on vmap for umem map
> samples: bpf: syscal_nrs: use mmap2 if defined
>
> net/xdp/xdp_umem.c | 36 +++++++++++++++++++++++-----
> samples/bpf/syscall_nrs.c | 6 +++++
> samples/bpf/tracex5_kern.c | 13 ++++++++++
> tools/lib/bpf/Makefile | 1 +
> tools/lib/bpf/xsk.c | 49 +++++++++++---------------------------
> 5 files changed, 64 insertions(+), 41 deletions(-)
>
Applied, and fixed up typo in last one's subject, thanks!
Powered by blists - more mailing lists