Received-SPF: pass (google.com: domain of linux-kernel+bounces-36378-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: haiyangz@microsoft.com, wei.liu@kernel.org, decui@microsoft.com,
        jejb@linux.ibm.com, linux-kernel@vger.kernel.org,
        linux-hyperv@vger.kernel.org, linux-scsi@vger.kernel.org,
        mhkelley58@gmail.com
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH 1/1] scsi: storvsc: Fix ring buffer size calculation
Date: Tue, 23 Jan 2024 22:00:43 -0500
Message-ID: <170606516777.594851.3500343804163840490.b4-ty@oracle.com>
In-Reply-To: <20240122170956.496436-1-mhklinux@outlook.com>
References: <20240122170956.496436-1-mhklinux@outlook.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

On Mon, 22 Jan 2024 09:09:56 -0800, mhkelley58@gmail.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