[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090414163312.C674.A69D9226@jp.fujitsu.com>
Date: Tue, 14 Apr 2009 16:42:17 +0900 (JST)
From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To: Wu Fengguang <fengguang.wu@...el.com>
Cc: kosaki.motohiro@...fujitsu.com,
Andrew Morton <akpm@...ux-foundation.org>,
Andi Kleen <andi@...stfloor.org>,
LKML <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: [RFC][PATCH] proc: export more page flags in /proc/kpageflags
> > > > > - PG_unevictable
> > > > > - PG_mlocked
>
> How about including PG_unevictable/PG_mlocked?
> They shall be meaningful to administrators.
I explained another mail. please see it.
> > this 9 flags shouldn't exported.
> > I can't imazine administrator use what purpose those flags.
>
> > > > > - PG_swapcache
> > > > > - PG_swapbacked
> > > > > - PG_poison
> > > > > - PG_compound
> >
> > I can agree this 4 flags.
> > However pagemap lack's hugepage considering.
> > if PG_compound exporting, we need more work.
>
> You mean to fold PG_head/PG_tail into PG_COMPOUND?
> Yes, that's a good simplification for end users.
Yes, I agree.
> > > > > - PG_NOPAGE: whether the page is present
> >
> > PM_NOT_PRESENT isn't enough?
>
> That would not be usable if you are going to do a system wide scan.
> PG_NOPAGE could help differentiate the 'no page' case from 'no flags'
> case.
>
> However PG_NOPAGE is more about the last resort. The system wide scan
> can be made much more efficient if we know the exact memory layouts.
Yup :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists