lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAHApi-mXt27N0dWW1QN5qZ6OOV9uVGxc-kuEd+SBF8hDJ2NPXA@mail.gmail.com> Date: Tue, 4 Apr 2023 14:37:27 +0200 From: Kal Cutter Conley <kal.conley@...tris.com> To: Magnus Karlsson <magnus.karlsson@...il.com> Cc: Björn Töpel <bjorn@...nel.org>, Magnus Karlsson <magnus.karlsson@...el.com>, Maciej Fijalkowski <maciej.fijalkowski@...el.com>, Jonathan Lemon <jonathan.lemon@...il.com>, "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, Jonathan Corbet <corbet@....net>, Alexei Starovoitov <ast@...nel.org>, Daniel Borkmann <daniel@...earbox.net>, Jesper Dangaard Brouer <hawk@...nel.org>, John Fastabend <john.fastabend@...il.com>, netdev@...r.kernel.org, bpf@...r.kernel.org, linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH bpf-next v2 08/10] xsk: Support UMEM chunk_size > PAGE_SIZE > > > > > > Is not the max 64K as you test against XDP_UMEM_MAX_CHUNK_SIZE in > > > > > > xdp_umem_reg()? > > > > > > > > > > The absolute max is 64K. In the case of HPAGE_SIZE < 64K, then it > > > > > would be HPAGE_SIZE. > > > > > > > > Is there such a case when HPAGE_SIZE would be less than 64K? If not, > > > > then just write 64K. > > > > > > Yes. While most platforms have HPAGE_SIZE defined to a compile-time > > > constant >= 64K (very often 2M) there are platforms (at least ia64 and > > > powerpc) where the hugepage size is configured at boot. Specifically, > > > in the case of Itanium (ia64), the hugepage size may be configured at > > > boot to any valid page size > PAGE_SIZE (e.g. 8K). See: > > > https://elixir.bootlin.com/linux/latest/source/arch/ia64/mm/hugetlbpage.c#L159 > > > > So for all practical purposes it is max 64K. Let us just write that then. > > What about when CONFIG_HUGETLB_PAGE is not defined? Should we keep it > set to PAGE_SIZE in that case, or would you like it to be a fixed > constant == 64K always? Sorry. Now it's not clear to me if you are suggesting the documentation be changed or the code or both?
Powered by blists - more mailing lists