From: Eric Sandeen <sandeen@sandeen.net>
To: "Martin K. Petersen" <mkp@mkp.net>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: discard_zeroes_data questions
Date: Mon, 9 Nov 2015 17:08:38 -0600 [thread overview]
Message-ID: <56412776.6080604@sandeen.net> (raw)
Hi Martin (and linux-ext4 list...)
tl;dr:
mke2fs today thinks that if discard_zeroes_data == 1 and a BLKDISCARD ioctl of the whole device succeeds, then we have guarantees that any blocks read back will be full of zero, and we don't need to initialize them to zero. Is this ok? (barring crappy hardware, that is).
slightly longer:
Does discard_zeroes_data == 1 mean that a discard *request* will guarantee zeroes on a read, or does it mean that a discard-request-which-actually-was-executed-and-not-ignored-as-just-a-hint will give us back zeroes on a read? (because UNMAP is a hint, right? I don't know about SATA trim ...)
I did see 7985090 sd: disable discard_zeroes_data for UNMAP - so I think that for v3.19+, on *scsi*, what e2fsprogs is doing is ok (now).
But I'm wondering about dm-thin and SATA, too, so trying to figure out what discard_zeroes_data really implies. That after a BLKDISCARD, a read *will* return zeros, or that it'll return zeros *iff* the hint is taken?
I hope that made sense, but I've been communicating badly today. ;)
Thanks,
-Eric
next reply other threads:[~2015-11-09 23:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 23:08 Eric Sandeen [this message]
2015-11-09 23:38 ` discard_zeroes_data questions Darrick J. Wong
2015-11-10 0:16 ` Martin K. Petersen
2015-11-10 0:15 ` Martin K. Petersen
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=56412776.6080604@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-ext4@vger.kernel.org \
--cc=mkp@mkp.net \
/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