From: Andrew Morton <akpm@linux-foundation.org>
To: "Theodore Ts'o" <tytso@mit.edu>, Alex Tomas <alex@clusterfs.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: booked-page-flag.patch
Date: Thu, 15 Feb 2007 00:45:04 -0800 [thread overview]
Message-ID: <20070215004504.023a90f0.akpm@linux-foundation.org> (raw)
Sorry, we're seriously, seriously, seriously short on flags in the page
struct and this patch is going to need one heck of a good case for it to be
acceptable.
Even then, we should put a lot of effort into finding some way of avoiding
adding that page flag. One option might be to add a new radix-tree tag,
and defining it as "for filesytem usage". Or use PG_checked (which should
be renamed to to PG_fs_misc) (if that doesn't conflict with ext4's existing
use of PG_checked). Or use !PageMappedToDisk()?
These patches seem to have a number of issues - we should get them properly
commented and properly changelogged then get them on the wire for decent
review before investing too much in them, please.
next reply other threads:[~2007-02-15 8:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 8:45 Andrew Morton [this message]
2007-02-15 14:03 ` booked-page-flag.patch Alex Tomas
2007-02-15 17:18 ` booked-page-flag.patch Eric Sandeen
2007-02-15 17:30 ` booked-page-flag.patch Alex Tomas
2007-02-15 20:56 ` booked-page-flag.patch Andrew Morton
2007-02-15 21:07 ` booked-page-flag.patch Alex Tomas
2007-02-15 23:23 ` booked-page-flag.patch Andrew Morton
2007-02-16 7:30 ` booked-page-flag.patch Alex Tomas
2007-02-16 7:46 ` booked-page-flag.patch Andrew Morton
2007-02-16 7:56 ` booked-page-flag.patch Alex Tomas
2007-02-16 8:06 ` booked-page-flag.patch Andrew Morton
2007-02-16 12:14 ` booked-page-flag.patch Andreas Dilger
2007-02-16 16:02 ` booked-page-flag.patch Dave Kleikamp
2007-02-16 15:03 ` booked-page-flag.patch Theodore Tso
2007-02-15 20:21 ` booked-page-flag.patch Andrew Morton
2007-02-16 12:17 ` booked-page-flag.patch 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=20070215004504.023a90f0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alex@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).