From: Chris Mason <chris.mason@oracle.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [patch][rfc] mm: new address space calls
Date: Wed, 25 Feb 2009 15:59:57 -0500 [thread overview]
Message-ID: <1235595597.32346.77.camel@think.oraclecorp.com> (raw)
In-Reply-To: <20090225104839.GG22785@wotan.suse.de>
On Wed, 2009-02-25 at 11:48 +0100, Nick Piggin wrote:
> This is about the last change to generic code I need for fsblock.
> Comments?
>
Thanks for doing this.
We've got releasepage, invalidatepage, and now release, all with
slightly different semantics and some complex interactions with the rest
of the VM.
One problem I have with the btrfs extent state code is that I might
choose to release the extent state in releasepage, but the VM might not
choose to free the page. So I've got an up to date page without any of
the rest of my state.
Which of these ops covers that? ;) I'd love to help better document the
requirements for these callbacks, I find it confusing every time.
-chris
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-02-25 20:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 10:48 [patch][rfc] mm: new address space calls Nick Piggin
2009-02-25 20:59 ` Chris Mason [this message]
2009-02-26 5:17 ` Nick Piggin
2009-02-26 13:21 ` Chris Mason
2009-02-27 11:26 ` Nick Piggin
2009-02-27 13:52 ` Chris Mason
2009-02-28 5:52 ` Nick Piggin
2009-02-28 23:19 ` Christoph Hellwig
2009-03-01 2:38 ` Nick Piggin
2009-02-28 23:24 ` Christoph Hellwig
2009-03-01 2:45 ` Nick Piggin
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=1235595597.32346.77.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
/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).