From: Christoph Hellwig <hch@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/3] vfs: Implement generic per-cpu counters for delayed allocation
Date: Sat, 9 Oct 2010 03:44:46 -0400 [thread overview]
Message-ID: <20101009074446.GA15551@infradead.org> (raw)
In-Reply-To: <1286583147-14760-3-git-send-email-jack@suse.cz>
On Sat, Oct 09, 2010 at 02:12:26AM +0200, Jan Kara wrote:
> Implement free blocks and reserved blocks counters for delayed allocation.
> These counters are reliable in the sence that when they return success, the
> subsequent conversion from reserved to allocated blocks always succeeds (see
> comments in the code for details). This is useful for ext3 filesystem to
> implement delayed allocation in particular for allocation in page_mkwrite.
This doesn't really look like generic code that should go into the core
kernel. I'd just add it to ext3 directly.
next prev parent reply other threads:[~2010-10-09 7:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-09 0:12 [PATCH RFC 0/3] Block reservation for ext3 Jan Kara
2010-10-09 0:12 ` [PATCH 1/3] vfs: Unmap underlying metadata of new data buffers only when buffer is mapped Jan Kara
2010-10-09 0:12 ` [PATCH 2/3] vfs: Implement generic per-cpu counters for delayed allocation Jan Kara
2010-10-09 7:44 ` Christoph Hellwig [this message]
2010-10-09 0:12 ` [PATCH 3/3] ext3: Implement delayed allocation on page_mkwrite time Jan Kara
2010-10-09 18:03 ` [PATCH RFC 0/3] Block reservation for ext3 Ted Ts'o
2010-10-11 14:28 ` Jan Kara
2010-10-11 21:59 ` Andrew Morton
2010-10-12 23:14 ` Jan Kara
2010-10-13 0:17 ` Ted Ts'o
[not found] ` <AANLkTimqbW7+wsXVoLa1Tx0K3VaDfrYKUE8owyD1VUxO@mail.gmail.com>
2010-10-13 8:49 ` Amir G.
2010-10-13 16:14 ` Amir G.
2010-10-14 15:57 ` Jan Kara
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=20101009074446.GA15551@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--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.