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: <20230817091554.31bb3600@kernel.org> Date: Thu, 17 Aug 2023 09:15:54 -0700 From: Jakub Kicinski <kuba@...nel.org> To: Ilias Apalodimas <ilias.apalodimas@...aro.org>, Mina Almasry <almasrymina@...gle.com> Cc: Yunsheng Lin <linyunsheng@...wei.com>, davem@...emloft.net, pabeni@...hat.com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, Lorenzo Bianconi <lorenzo@...nel.org>, Alexander Duyck <alexander.duyck@...il.com>, Liang Chen <liangchen.linux@...il.com>, Alexander Lobakin <aleksander.lobakin@...el.com>, Saeed Mahameed <saeedm@...dia.com>, Leon Romanovsky <leon@...nel.org>, Eric Dumazet <edumazet@...gle.com>, Jesper Dangaard Brouer <hawk@...nel.org> Subject: Re: [PATCH net-next v7 1/6] page_pool: frag API support for 32-bit arch with 64-bit DMA On Thu, 17 Aug 2023 16:57:16 +0300 Ilias Apalodimas wrote: > Why should we care about this? Even an architecture that's 32-bit and > has a 64bit DMA should be allowed to split the pages internally if it > decides to do so. The trick that drivers usually do is elevate the > page refcnt and deal with that internally. Can we assume the DMA mapping of page pool is page aligned? We should be, right? That means we're storing 12 bits of 0 at the lower end. So even with 32b of space we can easily store addresses for 32b+12b => 16TB of memory. "Ought to be enough" to paraphrase Bill G, and the problem is only in our heads? Before we go that way - Mina, are the dma-buf "chunks" you're working with going to be fragment-able? Or rather can driver and/or core take multiple references on a single buffer?
Powered by blists - more mailing lists