From: "Yang, Xiao/杨 晓" <yangx.jy@fujitsu.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: "zlang@redhat.com" <zlang@redhat.com>,
"fstests@vger.kernel.org" <fstests@vger.kernel.org>,
"bfoster@redhat.com" <bfoster@redhat.com>,
"Yasunori Gotou (Fujitsu)" <y-goto@fujitsu.com>
Subject: Re: [PATCH RESEND 2/2] generic/470: Replace thin volume with blkdiscard -z
Date: Mon, 14 Nov 2022 16:38:40 +0800 [thread overview]
Message-ID: <f45be313-a1a6-7f1a-9289-3a7d95c78551@fujitsu.com> (raw)
In-Reply-To: <Y3EwIvDfZdIlzHKg@magnolia>
On 2022/11/14 1:57, Darrick J. Wong wrote:
> You used -z, which means the comment should say "Forcibly zero the
> mapped range of the scratch device..." and note that blkdiscard -z will
> fall back to writing buffers of zeroes if the device doesn't support
> WRITE SAME with zeroes.
>
> I think the logic in here looks good though.
>
> --D
Hi Darrick,
Thanks a lot for your comment.
I have sent the v2 patch set[1][2] as you suggested. I hope you can
review them again.
[1]
https://lore.kernel.org/fstests/1668414903-13-1-git-send-email-yangx.jy@fujitsu.com/T/#t
[2]
https://lore.kernel.org/fstests/1668414903-13-2-git-send-email-yangx.jy@fujitsu.com/T/#u
Best Regards,
Xiao Yang
next prev parent reply other threads:[~2022-11-14 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 6:48 [PATCH RESEND 1/2] common/dmlogwrites: Extend _log_writes_init() to accept the specified size yangx.jy
2022-10-23 6:48 ` [PATCH RESEND 2/2] generic/470: Replace thin volume with blkdiscard -z yangx.jy
2022-10-24 4:09 ` Darrick J. Wong
2022-10-24 7:15 ` Yang, Xiao/杨 晓
2022-10-30 7:30 ` yangx.jy
2022-11-01 3:48 ` Darrick J. Wong
2022-11-12 5:48 ` Yang, Xiao/杨 晓
2022-11-13 17:57 ` Darrick J. Wong
2022-11-14 8:38 ` Yang, Xiao/杨 晓 [this message]
2022-11-13 17:54 ` [PATCH RESEND 1/2] common/dmlogwrites: Extend _log_writes_init() to accept the specified size Darrick J. Wong
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=f45be313-a1a6-7f1a-9289-3a7d95c78551@fujitsu.com \
--to=yangx.jy@fujitsu.com \
--cc=bfoster@redhat.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=y-goto@fujitsu.com \
--cc=zlang@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).