From: Theodore Ts'o <tytso@mit.edu>
To: "Lukáš Czerner" <lczerner@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Metadata reservation for unwritten extent conversion
Date: Wed, 13 Mar 2013 23:21:18 -0400 [thread overview]
Message-ID: <20130314032118.GA11821@thunk.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1303131830570.18319@dhcp-1-104.brq.redhat.com>
On Wed, Mar 13, 2013 at 06:31:25PM +0100, Lukáš Czerner wrote:
> > That sounds like the best thing to do. I assume you will be simply
> > taking the da_reserve_metadata() function introduced in the
> > to-be-dropped commit:
> >
> > > ext4: Reserve metadata if writing into uninitialized
> >
> > ... and moving it into the "reserve metadata block for every delayed
> > write" patch?
I wnated to kick off some testing tonight, so I've made this change to
the git tree. So the new version of "reserve metadata block for every
delayed write" is here:
https://git.kernel.org/cgit/linux/kernel/git/tytso/ext4.git/commit/?h=dev&id=c7cf7abbf754f16b78a8b9641d06baac6be60524
... and the dev branch has been modified to drop the "reserve metadata
if writing into unitialized.." commit.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-03-14 3:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 15:48 Metadata reservation for unwritten extent conversion Lukáš Czerner
2013-03-13 16:09 ` Lukáš Czerner
2013-03-13 17:25 ` Theodore Ts'o
2013-03-13 17:31 ` Lukáš Czerner
2013-03-14 3:21 ` Theodore Ts'o [this message]
2013-03-14 6:38 ` Metadata reservation for unwritten extent conversionjkj Lukáš Czerner
2013-03-14 7:08 ` [PATCH v2] ext4: reserve metadata block for every delayed write Lukas Czerner
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=20130314032118.GA11821@thunk.org \
--to=tytso@mit.edu \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.