[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2D5AB510-F3F1-4215-B9D6-CE576CC474B0@flugsvamp.com>
Date: Thu, 15 Aug 2019 12:33:44 -0700
From: "Jonathan Lemon" <jlemon@...gsvamp.com>
To: "Ivan Khoronzhuk" <ivan.khoronzhuk@...aro.org>
Cc: magnus.karlsson@...el.com, bjorn.topel@...el.com,
davem@...emloft.net, hawk@...nel.org, john.fastabend@...il.com,
jakub.kicinski@...ronome.com, daniel@...earbox.net,
netdev@...r.kernel.org, bpf@...r.kernel.org,
xdp-newbies@...r.kernel.org, linux-kernel@...r.kernel.org,
yhs@...com, andrii.nakryiko@...il.com
Subject: Re: [PATCH bpf-next v2 2/3] xdp: xdp_umem: replace kmap on vmap for
umem map
On 15 Aug 2019, at 5:13, Ivan Khoronzhuk wrote:
> For 64-bit there is no reason to use vmap/vunmap, so use page_address
> as it was initially. For 32 bits, in some apps, like in samples
> xdpsock_user.c when number of pgs in use is quite big, the kmap
> memory can be not enough, despite on this, kmap looks like is
> deprecated in such cases as it can block and should be used rather
> for dynamic mm.
>
> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@...aro.org>
Acked-by: Jonathan Lemon <jonathan.lemon@...il.com>
Powered by blists - more mailing lists