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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251027081658.GA15229@lst.de>
Date: Mon, 27 Oct 2025 09:16:58 +0100
From: Christoph Hellwig <hch@....de>
To: Leon Romanovsky <leon@...nel.org>
Cc: Christoph Hellwig <hch@....de>, Jens Axboe <axboe@...nel.dk>,
	Keith Busch <kbusch@...nel.org>, Sagi Grimberg <sagi@...mberg.me>,
	linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-nvme@...ts.infradead.org
Subject: Re: [PATCH v3 2/2] block-dma: properly take MMIO path

On Mon, Oct 27, 2025 at 10:11:42AM +0200, Leon Romanovsky wrote:
> BTW, one can reorganize pci_p2pdma_map_type to make sure that
> PCI_P2PDMA_MAP_BUS_ADDR will be 2 and PCI_P2PDMA_MAP_THRU_HOST_BRIDGE
> will be 3, so it will be possible to take 2 bits per-type instead of 3.

Maybe.  I'd be happy to leave this as-is and then see if we can optimize
things once we grow more users.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ