From: Alex Chiang <achiang@hp.com>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
"Li, Haicheng" <haicheng.li@intel.com>
Subject: Re: [PATCH] page-types: decode flags directly from command line
Date: Wed, 4 Nov 2009 13:40:08 -0700 [thread overview]
Message-ID: <20091104204008.GA8211@ldl.fc.hp.com> (raw)
In-Reply-To: <20091104121832.GB26504@localhost>
Hi Fengguang,
* Wu Fengguang <fengguang.wu@intel.com>:
> On Wed, Nov 04, 2009 at 06:54:41AM +0800, Alex Chiang wrote:
> > Why is this useful? For instance, if you're using memory hotplug
> > and see this in /var/log/messages:
> >
> > kernel: removing from LRU failed 3836dd0/1/1e00000000000400
> >
> > It would be nice to decode those page flags without staring at
> > the source.
>
> In fact it's more than decode - encoding is also possible with the
> _same_ code! So maybe "-d" and help message will not be all that
> appropriate.
I'm sorry, I don't understand this use case, so I'm not sure what
you're asking me to do.
You're saying that a use case would be something like:
./page-types --encode referenced,mmap
0x0000000000000004
?
If that's what you're asking for, I guess I'm not sure why that's
so useful, but then again, I'm a vm n00b so there are probably
lots of things I don't understand. ;)
> > Example usage and output:
> >
> > linux-2.6/Documentation/vm$ ./page-types -d 0x1e00000000000400
> > flags page-count MB symbolic-flags long-symbolic-flags
> > 0x1e00000000000400 1 0 __________B_______________________buddy
> > total 1 0
>
> The output is a bit redundant - so does the code. Could you simplify
> them a bit?
Well, the code is redundant, but add_page() / show_summary() is a
simple sequence.
In contrast, I think I'd have to modify walk_addr_ranges() and
maybe walk_pfn() to do something special when we don't really
want to do any address space walking, and simply want to
decode/encode some user input.
Maybe I don't understand you fully? Could you give me a better
idea of what you're looking for?
As for the output, I'm just reusing show_summary(). Maybe we
don't need the flags, page-count, and MB columns, but again, the
patch would be more intrusisive because we'd have to teach
show_summary() about the special case.
Anyway, I'm happy to make changes closer to what you're looking
for, but I'd like some more guidance as to what you're expecting.
Thanks,
/ac
WARNING: multiple messages have this Message-ID (diff)
From: Alex Chiang <achiang@hp.com>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
"Li, Haicheng" <haicheng.li@intel.com>
Subject: Re: [PATCH] page-types: decode flags directly from command line
Date: Wed, 4 Nov 2009 13:40:08 -0700 [thread overview]
Message-ID: <20091104204008.GA8211@ldl.fc.hp.com> (raw)
In-Reply-To: <20091104121832.GB26504@localhost>
Hi Fengguang,
* Wu Fengguang <fengguang.wu@intel.com>:
> On Wed, Nov 04, 2009 at 06:54:41AM +0800, Alex Chiang wrote:
> > Why is this useful? For instance, if you're using memory hotplug
> > and see this in /var/log/messages:
> >
> > kernel: removing from LRU failed 3836dd0/1/1e00000000000400
> >
> > It would be nice to decode those page flags without staring at
> > the source.
>
> In fact it's more than decode - encoding is also possible with the
> _same_ code! So maybe "-d" and help message will not be all that
> appropriate.
I'm sorry, I don't understand this use case, so I'm not sure what
you're asking me to do.
You're saying that a use case would be something like:
./page-types --encode referenced,mmap
0x0000000000000004
?
If that's what you're asking for, I guess I'm not sure why that's
so useful, but then again, I'm a vm n00b so there are probably
lots of things I don't understand. ;)
> > Example usage and output:
> >
> > linux-2.6/Documentation/vm$ ./page-types -d 0x1e00000000000400
> > flags page-count MB symbolic-flags long-symbolic-flags
> > 0x1e00000000000400 1 0 __________B_______________________buddy
> > total 1 0
>
> The output is a bit redundant - so does the code. Could you simplify
> them a bit?
Well, the code is redundant, but add_page() / show_summary() is a
simple sequence.
In contrast, I think I'd have to modify walk_addr_ranges() and
maybe walk_pfn() to do something special when we don't really
want to do any address space walking, and simply want to
decode/encode some user input.
Maybe I don't understand you fully? Could you give me a better
idea of what you're looking for?
As for the output, I'm just reusing show_summary(). Maybe we
don't need the flags, page-count, and MB columns, but again, the
patch would be more intrusisive because we'd have to teach
show_summary() about the special case.
Anyway, I'm happy to make changes closer to what you're looking
for, but I'd like some more guidance as to what you're expecting.
Thanks,
/ac
--
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-11-04 20:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 22:54 [PATCH] page-types: decode flags directly from command line Alex Chiang
2009-11-03 22:54 ` Alex Chiang
2009-11-04 12:18 ` Wu Fengguang
2009-11-04 12:18 ` Wu Fengguang
2009-11-04 20:40 ` Alex Chiang [this message]
2009-11-04 20:40 ` Alex Chiang
2009-11-05 2:14 ` Wu Fengguang
2009-11-05 2:14 ` Wu Fengguang
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=20091104204008.GA8211@ldl.fc.hp.com \
--to=achiang@hp.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=fengguang.wu@intel.com \
--cc=haicheng.li@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.