From: Jeff Moyer <jmoyer@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] Draft Linux kernel interfaces for ZBC drives
Date: Mon, 03 Feb 2014 17:26:02 -0500 [thread overview]
Message-ID: <x49sirzrfyd.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20140203213836.GB22856@thunk.org> (Theodore Ts'o's message of "Mon, 3 Feb 2014 16:38:36 -0500")
"Theodore Ts'o" <tytso@mit.edu> writes:
> On Mon, Feb 03, 2014 at 04:01:15PM -0500, Jeff Moyer wrote:
>> "Theodore Ts'o" <tytso@mit.edu> writes:
>>
>> > * We can also further shrink the structure by removing the
>> > * z_checkpoint_offset element, since most of the time
>> > * z_write_ptr_offset and z_checkpoint_offset will be the same. The
>> > * only time they will be different is after a write is interrupted
>> > * via an unexpected power removal
>>
>> This may fall into the nit-picking category, but at runtime I'd expect
>> the write pointer and the checkpoint lba to be different more often than
>> not, unless you're doing all FUA writes, or are issuing flushes after
>> every write.
>
> Sure, but the only time we care is after an unexpected power removal,
> and I would expect that shortly after the system is rebooted, the file
> system or userspace storage space application would want to take care
> of dealing with recovery right away.
>
> So I'm not really proposing to track the z_checkpoint_offset except
> report writes to the storage device that might have failed due to
> power failures, since presumably this is the only time users of this
> interface would care.
I agree it would be silly to track the checkpoint lba. I only took
issue with your comment. ;-)
Cheers,
Jeff
next prev parent reply other threads:[~2014-02-03 22:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 5:38 [RFC] Draft Linux kernel interfaces for ZBC drives Theodore Ts'o
2014-01-31 13:07 ` Matthew Wilcox
2014-01-31 15:44 ` Theodore Ts'o
2014-02-03 21:01 ` Jeff Moyer
2014-02-03 21:07 ` Martin K. Petersen
2014-02-03 21:38 ` Theodore Ts'o
2014-02-03 22:26 ` Jeff Moyer [this message]
2014-02-03 21:03 ` Eric Sandeen
2014-02-03 22:17 ` Theodore Ts'o
2014-02-04 2:00 ` HanBin Yoon
2014-02-04 16:27 ` Theodore Ts'o
2014-02-11 18:43 ` [RFC] Draft Linux kernel interfaces for SMR/ZBC drives Theodore Ts'o
2014-02-11 19:04 ` Andreas Dilger
2014-02-11 19:53 ` Theodore Ts'o
2014-02-13 2:08 ` Andreas Dilger
2014-02-13 3:09 ` Theodore Ts'o
2014-02-21 10:02 ` [RFC] Draft Linux kernel interfaces for ZBC drives Rohan Puri
2014-02-21 15:49 ` Theodore Ts'o
2014-02-25 9:36 ` Rohan Puri
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=x49sirzrfyd.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).