[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241119182427.GA20997@lst.de>
Date: Tue, 19 Nov 2024 19:24:27 +0100
From: Christoph Hellwig <hch@....de>
To: Keith Busch <kbusch@...nel.org>
Cc: Christoph Hellwig <hch@....de>, Jens Axboe <axboe@...nel.dk>,
Christian Brauner <brauner@...nel.org>,
Sagi Grimberg <sagi@...mberg.me>,
Kanchan Joshi <joshi.k@...sung.com>, Hui Qi <hui81.qi@...sung.com>,
Nitesh Shetty <nj.shetty@...sung.com>, Jan Kara <jack@...e.cz>,
Pavel Begunkov <asml.silence@...il.com>,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-nvme@...ts.infradead.org, linux-fsdevel@...r.kernel.org,
io-uring@...r.kernel.org
Subject: Re: [PATCH 14/15] nvme: enable FDP support
On Tue, Nov 19, 2024 at 11:17:36AM -0700, Keith Busch wrote:
> > + if (le32_to_cpu(configs[result.fdpcidx].nrg) > 1) {
> > + dev_warn(ns->ctrl->device, "FDP NRG > 1 not supported\n");
>
> Why not support multiple reclaim groups?
Can you come up with a sane API for that? And can you find devices in
the wild that actually support it?
> > + ns->head->runs = le64_to_cpu(configs[result.fdpcidx].runs);
>
> The config descriptors are variable length, so you can't just index into
> it. You have to read each index individually to get the next index's offset.
> Something like:
Indeed. The current code only works when the first config is selected.
Powered by blists - more mailing lists