linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Bryan Henderson <hbryan@us.ibm.com>
To: pbadari@us.ibm.com
Cc: Andrew Morton <akpm@osdl.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: page flags ?
Date: Wed, 18 May 2005 16:57:09 -0700	[thread overview]
Message-ID: <OF5AB2212B.F152D3D7-ON88257005.00830C2C-88257005.00839F74@us.ibm.com> (raw)
In-Reply-To: <1116456143.26913.1303.camel@dyn318077bld.beaverton.ibm.com>

By the way, shouldn't these really be PG_as_misc/PG_as_specific as opposed 
to PG_fs_misc ...?

In theory, an address space can be something other than a file cache, and 
there's no reason any arbitrary adress_space_ops shouldn't have its own 
private flags.

--
Bryan Henderson                          IBM Almaden Research Center
San Jose CA                              Filesystems
--
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>

      parent reply	other threads:[~2005-05-18 23:58 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
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 [this message]

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=OF5AB2212B.F152D3D7-ON88257005.00830C2C-88257005.00839F74@us.ibm.com \
    --to=hbryan@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pbadari@us.ibm.com \
    /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