linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@gmail.com>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
	linux-mm@kvack.org, Kyungmin Park <kyungmin.park@samsung.com>,
	Matt Mackall <mpm@selenic.com>
Subject: Re: [PATCH 2/2] proc: add ARCH_PFN_OFFSET info to /proc/meminfo
Date: Mon, 04 Jun 2012 05:43:56 -0400	[thread overview]
Message-ID: <4FCC835C.3010007@gmail.com> (raw)
In-Reply-To: <201206041018.13568.b.zolnierkie@samsung.com>

(6/4/12 4:18 AM), Bartlomiej Zolnierkiewicz wrote:
> On Friday 01 June 2012 22:26:57 KOSAKI Motohiro wrote:
>> (6/1/12 12:54 PM), Bartlomiej Zolnierkiewicz wrote:
>>> From: Bartlomiej Zolnierkiewicz<b.zolnierkie@samsung.com>
>>> Subject: [PATCH] proc: add ARCH_PFN_OFFSET info to /proc/meminfo
>>>
>>> ARCH_PFN_OFFSET is needed for user-space to use together with
>>> /proc/kpage[count,flags] interfaces.
>>>
>>> Cc: Matt Mackall<mpm@selenic.com>
>>> Signed-off-by: Bartlomiej Zolnierkiewicz<b.zolnierkie@samsung.com>
>>> Signed-off-by: Kyungmin Park<kyungmin.park@samsung.com>
>>> ---
>>>    fs/proc/meminfo.c |    4 ++++
>>>    1 file changed, 4 insertions(+)
>>>
>>> Index: b/fs/proc/meminfo.c
>>> ===================================================================
>>> --- a/fs/proc/meminfo.c	2012-05-31 16:53:11.589706973 +0200
>>> +++ b/fs/proc/meminfo.c	2012-05-31 17:03:17.719237120 +0200
>>> @@ -168,6 +168,10 @@ static int meminfo_proc_show(struct seq_
>>>
>>>    	hugetlb_report_meminfo(m);
>>>
>>> +	seq_printf(m,
>>> +		"ArchPFNOffset:    %6lu\n",
>>> +		ARCH_PFN_OFFSET);
>>> +
>>>    	arch_report_meminfo(m);
>>
>> NAK.
>>
>> arch specific report should use arch_report_meminfo().
>
> ARCH_PFN_OFFSET is defined for all archs so I think that it makes little
> sense to duplicate it in every per-arch arch_report_meminfo()..

Incorrect. We are usually constant value for ARCH_PFN_OFFSET. so we don't need
any exporting.





--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2012-06-04  9:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-01 16:54 Bartlomiej Zolnierkiewicz
2012-06-01 20:26 ` KOSAKI Motohiro
2012-06-04  8:18   ` Bartlomiej Zolnierkiewicz
2012-06-04  9:43     ` KOSAKI Motohiro [this message]
2012-06-04 10:01       ` Bartlomiej Zolnierkiewicz

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=4FCC835C.3010007@gmail.com \
    --to=kosaki.motohiro@gmail.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-mm@kvack.org \
    --cc=mpm@selenic.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