linux-kernel - Re: [PATCH 1/1] scsi: storvsc: Fix ring buffer size calculation

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] [day] [month] [year] [list]

Date: Tue, 23 Jan 2024 22:00:43 -0500
From: "Martin K. Petersen" <martin.petersen@...cle.com>
To: haiyangz@...rosoft.com, wei.liu@...nel.org, decui@...rosoft.com,
        jejb@...ux.ibm.com, linux-kernel@...r.kernel.org,
        linux-hyperv@...r.kernel.org, linux-scsi@...r.kernel.org,
        mhkelley58@...il.com
Cc: "Martin K . Petersen" <martin.petersen@...cle.com>
Subject: Re: [PATCH 1/1] scsi: storvsc: Fix ring buffer size calculation

On Mon, 22 Jan 2024 09:09:56 -0800, mhkelley58@...il.com wrote:

> Current code uses the specified ring buffer size (either the default of
> 128 Kbytes or a module parameter specified value) to encompass the one page
> ring buffer header plus the actual ring itself.  When the page size is
> 4K, carving off one page for the header isn't significant.  But when the
> page size is 64K on ARM64, only half of the default 128 Kbytes is left
> for the actual ring.  While this doesn't break anything, the smaller
> ring size could be a performance bottleneck.
> 
> [...]

Applied to 6.8/scsi-fixes, thanks!

[1/1] scsi: storvsc: Fix ring buffer size calculation
      https://git.kernel.org/mkp/scsi/c/f4469f385835

-- 
Martin K. Petersen	Oracle Linux Engineering