issuing flush to all namespaces
Klaus Jensen
its at irrelevant.dk
Thu Jul 14 01:16:19 PDT 2022
On Jul 14 10:11, Christoph Hellwig wrote:
> On Thu, Jul 14, 2022 at 10:08:41AM +0200, Klaus Jensen wrote:
> > Hi,
> >
> > Since the (very reasonable) changes that cause the driver to check that
> > the nsid of the command corresponds to the nsid of the namespace being
> > targeted it is no longer possible to issue a flush to all namespaces:
> >
> > # nvme flush /dev/nvme0n1 -n 0xffffffff
> > flush: Invalid argument
> >
> > Now, I think we can all agree that Flush is the odd one out here, but
> > can we do anything about it? The char devices also check the nsid, so
> > they can't be used either.
>
> Don't do it. Sending flush to all namespaces wasn't even clearly
> defined until I think NVMe 1.4 with the supported bits. It doesn't
> really make much sense and there is no point in supporting it in Linux.
Alright, I hear you :) Thanks!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-nvme/attachments/20220714/0a11ca57/attachment.sig>
More information about the Linux-nvme
mailing list