[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <64ff1dcf9e46c15e062ccf05ae6f9efd3747f0fd.camel@icenowy.me>
Date: Tue, 25 Feb 2025 10:07:31 +0800
From: Icenowy Zheng <uwu@...nowy.me>
To: Keith Busch <kbusch@...nel.org>, Christoph Hellwig <hch@....de>
Cc: Jens Axboe <axboe@...nel.dk>, Sagi Grimberg <sagi@...mberg.me>,
linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] Misc fixes on registering PCI NVMe CMB
在 2025-02-24星期一的 17:17 -0700,Keith Busch写道:
> On Thu, Feb 13, 2025 at 06:54:49AM +0100, Christoph Hellwig wrote:
> > On Thu, Feb 13, 2025 at 01:04:42AM +0800, Icenowy Zheng wrote:
> > > Here is a small patchset that is developed during my
> > > investigation of
> > > a WARNING in my boot kernel log (AMD EPYC 7K62 CPU + Intel DC
> > > D4502
> > > SSD), which is because of the SSD's too-small CMB block (512KB
> > > only).
> >
> > Hah, that's certainly and odd CMB configuration.
>
> Should be okay if it's just for submission queues. The driver has an
> arbitrary requirement that the queues have at least 64 entries for
> CMB,
> and 512k allows us to create 128 submission queues like that. That's
> enough for most systems.
Yes, but this configuration seems to not fit the current driver code
that utilizes PCIe P2P setup code. (Is there any driver that could
utilize this configuration now?)
Powered by blists - more mailing lists