From: Ted Ts'o <tytso@mit.edu>
To: Bobi Jam <bobijam@whamcloud.com>
Cc: linux-ext4@vger.kernel.org, Andreas Dilger <adilger@whamcloud.com>
Subject: Re: [PATCH] ext4: expand commit callback
Date: Mon, 13 Feb 2012 16:02:25 -0500 [thread overview]
Message-ID: <20120213210225.GA21641@thunk.org> (raw)
In-Reply-To: <1319626156-2444-1-git-send-email-bobijam@whamcloud.com>
On Wed, Oct 26, 2011 at 06:49:16PM +0800, Bobi Jam wrote:
> The per-commit callback is now used by mballoc code to manage free
> space bitmaps after deleted blocks have been released. This patch
> expand it to contain multiple different callbacks.
>
> Signed-off-by: Bobi Jam <bobijam@whamcloud.com>
> Signed-off-by: Andreas Dilger <adilger@whamcloud.com>
Thanks, applied.
Note: since this callback is called *after* the commit is completed,
we can't really use this to do things like compute metadata checksums
or update atimes more efficiently, since those sorts of things have to
happen *before* we actually finish up the commit.
- Ted
next prev parent reply other threads:[~2012-02-13 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 10:49 [PATCH] ext4: expand commit callback Bobi Jam
2011-11-04 12:17 ` Bobi Jam
2012-02-13 21:02 ` Ted Ts'o [this message]
2012-02-13 23:50 ` 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=20120213210225.GA21641@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@whamcloud.com \
--cc=bobijam@whamcloud.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 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).