[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <yq1bkdfrt8l.fsf@ca-mkp.ca.oracle.com>
Date: Tue, 03 Oct 2023 23:00:55 -0400
From: "Martin K. Petersen" <martin.petersen@...cle.com>
To: Bart Van Assche <bvanassche@....org>
Cc: John Garry <john.g.garry@...cle.com>, axboe@...nel.dk,
kbusch@...nel.org, hch@....de, sagi@...mberg.me,
jejb@...ux.ibm.com, martin.petersen@...cle.com, djwong@...nel.org,
viro@...iv.linux.org.uk, brauner@...nel.org,
chandan.babu@...cle.com, dchinner@...hat.com,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-nvme@...ts.infradead.org, linux-xfs@...r.kernel.org,
linux-fsdevel@...r.kernel.org, tytso@....edu, jbongio@...gle.com,
linux-api@...r.kernel.org,
Himanshu Madhani <himanshu.madhani@...cle.com>
Subject: Re: [PATCH 01/21] block: Add atomic write operations to
request_queue limits
Bart,
> also that there are no guarantees that the data written by an atomic
> write will survive a power failure. See also the difference between
> the NVMe parameters AWUN and AWUPF.
We only care about *PF. The *N variants were cut from the same cloth as
TRIM and UNMAP.
--
Martin K. Petersen Oracle Linux Engineering
Powered by blists - more mailing lists