From: Badari Pulavarty <pbadari@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-mm@kvack.org, linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: page flags ?
Date: 18 May 2005 17:09:29 -0700 [thread overview]
Message-ID: <1116461369.26913.1339.camel@dyn318077bld.beaverton.ibm.com> (raw)
In-Reply-To: <20050518162302.13a13356.akpm@osdl.org>
On Wed, 2005-05-18 at 16:23, Andrew Morton wrote:
> Badari Pulavarty <pbadari@us.ibm.com> wrote:
> >
> > Is it possible to get yet another PG_fs_specific flag ?
>
> Anything's possible ;)
>
> How many bits are spare now? ZONETABLE_PGSHIFT hurts my brain.
Depends on whom you ask :) CKRM folks are using one/few,
Hotplug memory guys are using one... :( I lost track..
>
> > Reasons for it are:
> >
> > - I need this for supporting delayed allocation on ext3.
>
> Why?
>
I think, I explained you earlier.. But let me refresh your memory.
In order to do delayed allocation, we "reserve" (not same reservation
the code) a block in prepare/commit and do the allocation in
writepage/writepages. Unfortunately, mapped writes directly come into
writepage without making a reservation. In order to guarantee that
write() succeeds, I need a way to indicate if the "page" has made
a reservation or not. I was hoping to use a page->flag to do this.
That way I don't have to touch page->private like Alex's code and
get away using mpage routines, instead of having my own.
Thanks,
Badari
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-05-19 0:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 21:13 Badari Pulavarty
2005-05-18 21:56 ` Andrew Morton
2005-05-18 22:42 ` Badari Pulavarty
2005-05-18 23:23 ` Andrew Morton
2005-05-19 0:09 ` Badari Pulavarty [this message]
2005-05-19 0:26 ` Chandra Seetharaman
2005-05-19 1:36 ` Dave Hansen
2005-05-19 10:51 ` Andy Whitcroft
2005-05-19 11:11 ` Andrew Morton
2005-05-19 14:37 ` Nikita Danilov
2005-05-19 18:29 ` Badari Pulavarty
2005-05-19 22:53 ` Andrew Morton
2005-05-19 23:34 ` Badari Pulavarty
2005-05-20 0:03 ` Martin J. Bligh
2005-05-19 23:55 ` Badari Pulavarty
2005-05-20 0:20 ` Martin J. Bligh
2005-05-18 23:57 ` Bryan Henderson
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=1116461369.26913.1339.camel@dyn318077bld.beaverton.ibm.com \
--to=pbadari@us.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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