From: Jan Kara <jack@suse.cz>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Jan Kara <jack@suse.cz>, linux-ext4@vger.kernel.org
Subject: Re: A proposal for making ext4's journal more SMR (and flash) friendly
Date: Fri, 10 Jan 2014 07:04:29 +0100 [thread overview]
Message-ID: <20140110060429.GA26378@quack.suse.cz> (raw)
In-Reply-To: <20140108233752.GD17750@thunk.org>
On Wed 08-01-14 18:37:52, Ted Tso wrote:
> On Wed, Jan 08, 2014 at 11:14:30PM +0100, Jan Kara wrote:
> > 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?
>
> I think there are two interfaces that should handle nearly all of our
> journal block mapping needs. The functions that issue bio requests
> directly tend to use ext4_get_block*() functions, and functions which
> use the buffer cache uses submit_bh() (typically via ext4_getblk).
> There will probably be a few exceptions, but I don't think this should
> be an intractable problem.
Surely not intractable :) It was just ugly. But you are right that
hooking in ext4_map_blocks() and then special-casing the few cases where we
get the block number by different means (xattrs, inode table, group
descriptor, superblock, traversal of extent tree & indirect block tree)
should be reasonably elegant.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2014-01-10 6:04 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
2014-01-08 23:37 ` Theodore Ts'o
2014-01-10 6:04 ` Jan Kara [this message]
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=20140110060429.GA26378@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