From: "Martin J. Bligh" <mbligh@mbligh.org>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
apw@shadowen.org, linux-mm@kvack.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: page flags ?
Date: Thu, 19 May 2005 17:20:10 -0700 [thread overview]
Message-ID: <66070000.1116548410@flay> (raw)
In-Reply-To: <1116546938.26913.1386.camel@dyn318077bld.beaverton.ibm.com>
>> > BTW, I tried to kill PG_slab. Other than catching error conditions
>> > with memory freeing, there are few users of it
>> >
>> > - show_mem(): to show how much memory stuck in slab easily.
>> > - kobjsize()
>>
>> Is really useful to be able to trace down exactly what mem is in slab,
>> and otherwise were memory came from / leaked to. I spose it could could
>> be a debug option, but seems a bit sad if we don't need the space yet.
>> /proc/meminfo gets it from per cpu page_state, but is nice to have
>> a double check.
>
> I agree. I like that "memory stuck in slab" info too :)
> Shall we wait till we really really need bits in page->flags ?
> Hopefully, by then we will all be 64-bit and life would be wonderful :)
Would be nicer not to kill them until we need ... perhaps they could be
commented as to their potential demise? Then the debug ones could be
wrapped in something else, at least, and made available on 64 bit only
(when it comes to that ...)
M.
--
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-20 0:20 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 [this message]
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=66070000.1116548410@flay \
--to=mbligh@mbligh.org \
--cc=akpm@osdl.org \
--cc=apw@shadowen.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