From: Michal Nazarewicz <mina86@mina86.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Mel Gorman <mgorman@suse.de>, Andy Whitcroft <apw@shadowen.org>,
Alexander Nyberg <alexn@dsv.su.se>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v2 2/2] Enhance read_block of page_owner.c
Date: Mon, 14 Jan 2013 09:27:57 +0100 [thread overview]
Message-ID: <xa1t6230p3si.fsf@mina86.com> (raw)
In-Reply-To: <20130114023338.GB18097@blaptop>
[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]
On Mon, Jan 14 2013, Minchan Kim <minchan@kernel.org> wrote:
> I'm not familar with Python but I can see the point of the program.
> It's very short and good for maintainace but I have a concern about the size.
> For working it in embedded side, we have to port python in that
> machine. :( [...]
> In case of that, just small C program when we release product would be
> good choice.
But is this program intended to be used as is? Or rather to serve as an
example? If the former, than I think it should be in tools/ rather than
in Documentation/. If the latter, than I think it does not really
matter whether it's C or some scripting language, since the purpose is
to show how /proc/page_owner can be used, and in fact showing the
general idea may be simpler with a shorter program which does not have
to deal with memory management.
And if Python is not your fancy, you can always use some shell: ;)
awk -vRS= '{ gsub("\n", "\\n"); print $0 }' |sort |uniq -c
> But I'm not strong aginst on your simple python program. If it is merged,
> we will just continue to use C program instead of python's one.
> If you have a strong opinion, send it to akpm as separate patch.
Not at all. I'm just throwing ideas.
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michał “mina86” Nazarewicz (o o)
ooo +----<email/xmpp: mpn@google.com>--------------ooO--(_)--Ooo--
[-- Attachment #2.1: Type: text/plain, Size: 0 bytes --]
[-- Attachment #2.2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2013-01-14 8:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 2:30 [PATCH v2 1/2] Fix wrong EOF compare Minchan Kim
2013-01-11 2:30 ` Minchan Kim
2013-01-11 2:30 ` [PATCH v2 2/2] Enhance read_block of page_owner.c Minchan Kim
2013-01-11 2:30 ` Minchan Kim
2013-01-11 16:01 ` Michal Nazarewicz
2013-01-11 16:01 ` Michal Nazarewicz
2013-01-14 2:33 ` Minchan Kim
2013-01-14 2:33 ` Minchan Kim
2013-01-14 8:27 ` Michal Nazarewicz [this message]
2013-01-11 14:21 ` [PATCH v2 1/2] Fix wrong EOF compare Michal Nazarewicz
2013-01-11 14:21 ` Michal Nazarewicz
2013-01-13 11:44 ` Rob Landley
2013-01-13 11:44 ` Rob Landley
2013-01-13 18:15 ` Randy Dunlap
2013-01-13 18:15 ` Randy Dunlap
2013-01-31 10:25 ` Rob Landley
2013-01-31 10:25 ` Rob Landley
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=xa1t6230p3si.fsf@mina86.com \
--to=mina86@mina86.com \
--cc=akpm@linux-foundation.org \
--cc=alexn@dsv.su.se \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=rdunlap@infradead.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.