From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Damien Le Moal <dlemoal@kernel.org>, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org
Subject: Re: [PATCH 2/2] zloop: forget write cache on force removal
Date: Thu, 19 Mar 2026 10:04:59 -0400 [thread overview]
Message-ID: <yq18qbnnch1.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20260319060246.2084931-3-hch@lst.de> (Christoph Hellwig's message of "Thu, 19 Mar 2026 07:02:37 +0100")
Christoph,
> +discard_write_cache Discard all data that was not explicitly persisted using a
> + flush operation when the devie is removed by truncating
^^^^^
device
Otherwise OK.
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
--
Martin K. Petersen
next prev parent reply other threads:[~2026-03-19 14:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 6:02 add a "discard cache" debug option to zloop v2 Christoph Hellwig
2026-03-19 6:02 ` [PATCH 1/2] zloop: refactor zloop_rw Christoph Hellwig
2026-03-19 14:06 ` Martin K. Petersen
2026-03-19 6:02 ` [PATCH 2/2] zloop: forget write cache on force removal Christoph Hellwig
2026-03-19 14:04 ` Martin K. Petersen [this message]
2026-03-19 21:18 ` add a "discard cache" debug option to zloop v2 Bart Van Assche
-- strict thread matches above, loose matches on Subject: below --
2026-03-23 7:11 add a "discard cache" debug option to zloop v3 Christoph Hellwig
2026-03-23 7:11 ` [PATCH 2/2] zloop: forget write cache on force removal Christoph Hellwig
2026-03-18 5:53 add a "discard cache" debug option to zloop Christoph Hellwig
2026-03-18 5:53 ` [PATCH 2/2] zloop: forget write cache on force removal Christoph Hellwig
2026-03-18 7:03 ` Damien Le Moal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yq18qbnnch1.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox