From: Daniel Borkmann <daniel@iogearbox.net>
To: Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>,
magnus.karlsson@intel.com, bjorn.topel@intel.com
Cc: davem@davemloft.net, hawk@kernel.org, john.fastabend@gmail.com,
jakub.kicinski@netronome.com, netdev@vger.kernel.org,
bpf@vger.kernel.org, xdp-newbies@vger.kernel.org,
linux-kernel@vger.kernel.org, jlemon@flugsvamp.com, yhs@fb.com,
andrii.nakryiko@gmail.com
Subject: Re: [PATCH bpf-next v2 0/3] xdpsock: allow mmap2 usage for 32bits
Date: Wed, 21 Aug 2019 14:35:19 +0200 [thread overview]
Message-ID: <95fb201c-1623-149b-a72e-ed4860f742e1@iogearbox.net> (raw)
In-Reply-To: <20190815121356.8848-1-ivan.khoronzhuk@linaro.org>
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!
prev parent reply other threads:[~2019-08-21 12:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 12:13 [PATCH bpf-next v2 0/3] xdpsock: allow mmap2 usage for 32bits Ivan Khoronzhuk
2019-08-15 12:13 ` [PATCH bpf-next v2 1/3] libbpf: use LFS (_FILE_OFFSET_BITS) instead of direct mmap2 syscall Ivan Khoronzhuk
2019-08-16 0:06 ` Yonghong Song
2019-08-15 12:13 ` [PATCH bpf-next v2 2/3] xdp: xdp_umem: replace kmap on vmap for umem map Ivan Khoronzhuk
2019-08-15 18:23 ` Jonathan Lemon
2019-08-15 19:19 ` Ivan Khoronzhuk
2019-08-15 19:32 ` Jonathan Lemon
2019-08-15 19:33 ` Jonathan Lemon
2019-08-15 12:13 ` [PATCH bpf-next v2 3/3] samples: bpf: syscal_nrs: use mmap2 if defined Ivan Khoronzhuk
2019-08-19 21:17 ` Jonathan Lemon
2019-08-21 12:35 ` Daniel Borkmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=95fb201c-1623-149b-a72e-ed4860f742e1@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=andrii.nakryiko@gmail.com \
--cc=bjorn.topel@intel.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=ivan.khoronzhuk@linaro.org \
--cc=jakub.kicinski@netronome.com \
--cc=jlemon@flugsvamp.com \
--cc=john.fastabend@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=xdp-newbies@vger.kernel.org \
--cc=yhs@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox