public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: A proposal for making ext4's journal more SMR (and flash) friendly
Date: Wed, 8 Jan 2014 23:14:30 +0100	[thread overview]
Message-ID: <20140108221430.GB21663@quack.suse.cz> (raw)
In-Reply-To: <nsxfvozavl2.fsf@lambda.thunk.org>

On Wed 08-01-14 00:31:05, Ted Tso wrote:
> The simplest implementation of this design does not require making any
> on-disk format changes.  We simply suppress the writeback of the dirty
> metadata block to the file system.  Instead we keep a journal map in
> memory, which maps metadata block numbers (or data block numbers if data
> journalling is enabled) to a block number in the journal.
> 
> The journal is not truncated when the file system is unmounted, and so
> there is no difference between mounting a file system which has been
> cleanly unmounted or after a system crash.  In both case, the ext4 file
> system will scan the journal, and create an in-memory data structure
> which maps metadata block locations to their location in the journal.
> When a metadata block (or a data block, if data journalling is enabled)
> needs to be read, if the block number is found in the journal map, the
> block is read from the journal instead of from its "real" location on
> disk.
  So when I was thinking about this (already couple of years ago) the thing
which stopped me was the question at which layer we should do the
translation. Ideally we would need something at submit_bh() level but just
wrapping submit_bh() calls inside ext4 isn't enough for stuff like symlinks
or journalled data... Do you have any thoughts on that?

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  parent reply	other threads:[~2014-01-08 22:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08  5:31 A proposal for making ext4's journal more SMR (and flash) friendly Theodore Ts'o
2014-01-08 11:43 ` Lukáš Czerner
2014-01-08 15:20   ` Theodore Ts'o
2014-01-08 15:45     ` Lukáš Czerner
2014-01-08 22:14 ` Jan Kara [this message]
2014-01-08 23:37   ` Theodore Ts'o
2014-01-10  6:04     ` Jan Kara
2014-01-10 16:32       ` Theodore Ts'o
2014-01-09  3:55 ` Andreas Dilger
2014-01-09 13:41   ` Theodore Ts'o
2014-01-10  8:14     ` Andreas Dilger

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=20140108221430.GB21663@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=linux-ext4@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