From: Xishi Qiu <qiuxishi@huawei.com>
To: Michal Nazarewicz <mina86@mina86.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
m.szyprowski@samsung.com, aneesh.kumar@linux.vnet.ibm.com,
iamjoonsoo.kim@lge.com, LKML <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH] CMA: add the amount of cma memory in meminfo
Date: Fri, 5 Dec 2014 09:42:12 +0800 [thread overview]
Message-ID: <54810D74.4030606@huawei.com> (raw)
In-Reply-To: <xa1tfvcvcrey.fsf@mina86.com>
On 2014/12/5 0:26, Michal Nazarewicz wrote:
> On Thu, Dec 04 2014, Xishi Qiu <qiuxishi@huawei.com> wrote:
>> Add the amount of cma memory in the following meminfo.
>> /proc/meminfo
>> /sys/devices/system/node/nodeXX/meminfo
>>
>> Signed-off-by: Xishi Qiu <qiuxishi@huawei.com>
>> ---
>> drivers/base/node.c | 16 ++++++++++------
>> fs/proc/meminfo.c | 12 +++++++++---
>> 2 files changed, 19 insertions(+), 9 deletions(-)
>>
>> diff --git a/drivers/base/node.c b/drivers/base/node.c
>> index 472168c..a27e4e0 100644
>> --- a/drivers/base/node.c
>> +++ b/drivers/base/node.c
>> @@ -120,6 +120,9 @@ static ssize_t node_read_meminfo(struct device *dev,
>> #ifdef CONFIG_TRANSPARENT_HUGEPAGE
>> "Node %d AnonHugePages: %8lu kB\n"
>> #endif
>> +#ifdef CONFIG_CMA
>> + "Node %d FreeCMAPages: %8lu kB\n"
>> +#endif
>> ,
>> nid, K(node_page_state(nid, NR_FILE_DIRTY)),
>> nid, K(node_page_state(nid, NR_WRITEBACK)),
>> @@ -136,14 +139,15 @@ static ssize_t node_read_meminfo(struct device *dev,
>> nid, K(node_page_state(nid, NR_SLAB_RECLAIMABLE) +
>> node_page_state(nid, NR_SLAB_UNRECLAIMABLE)),
>> nid, K(node_page_state(nid, NR_SLAB_RECLAIMABLE)),
>> -#ifdef CONFIG_TRANSPARENT_HUGEPAGE
>> nid, K(node_page_state(nid, NR_SLAB_UNRECLAIMABLE))
>
> Why is this line suddenly out of a??#ifdef CONFIG_TRANSPARENT_HUGEPAGEa???
>
Hi Michal,
The original code is like this.
...
#ifdef CONFIG_TRANSPARENT_HUGEPAGE
nid, K(node_page_state(nid, NR_SLAB_UNRECLAIMABLE))
, nid,
K(node_page_state(nid, NR_ANON_TRANSPARENT_HUGEPAGES) *
HPAGE_PMD_NR));
#else
nid, K(node_page_state(nid, NR_SLAB_UNRECLAIMABLE)));
#endif
...
I change it to like this, just move ");" out of the "#ifdef".
...
nid, K(node_page_state(nid, NR_SLAB_UNRECLAIMABLE))
#ifdef CONFIG_TRANSPARENT_HUGEPAGE
, nid, K(node_page_state(nid,
NR_ANON_TRANSPARENT_HUGEPAGES) * HPAGE_PMD_NR)
#endif
);
...
>> - , nid,
>> - K(node_page_state(nid, NR_ANON_TRANSPARENT_HUGEPAGES) *
>> - HPAGE_PMD_NR));
>> -#else
>> - nid, K(node_page_state(nid, NR_SLAB_UNRECLAIMABLE)));
>> +#ifdef CONFIG_TRANSPARENT_HUGEPAGE
>> + , nid, K(node_page_state(nid,
>> + NR_ANON_TRANSPARENT_HUGEPAGES) * HPAGE_PMD_NR)
>
> This is mere white-space change which is confusing.
>
you mean change like this ", nid, K(...)" -> ",nid, K(xxx)"?
Thanks,
Xishi Qiu
>> +#endif
>> +#ifdef CONFIG_CMA
>> + , nid, K(node_page_state(nid, NR_FREE_CMA_PAGES))
>> #endif
>> + );
>> n += hugetlb_report_node_meminfo(nid, buf + n);
>> return n;
>> }
>> diff --git a/fs/proc/meminfo.c b/fs/proc/meminfo.c
>> index aa1eee0..d42e082 100644
>> --- a/fs/proc/meminfo.c
>> +++ b/fs/proc/meminfo.c
>> @@ -138,6 +138,9 @@ static int meminfo_proc_show(struct seq_file *m, void *v)
>> #ifdef CONFIG_TRANSPARENT_HUGEPAGE
>> "AnonHugePages: %8lu kB\n"
>> #endif
>> +#ifdef CONFIG_CMA
>> + "FreeCMAPages: %8lu kB\n"
>> +#endif
>> ,
>> K(i.totalram),
>> K(i.freeram),
>> @@ -187,11 +190,14 @@ static int meminfo_proc_show(struct seq_file *m, void *v)
>> vmi.used >> 10,
>> vmi.largest_chunk >> 10
>> #ifdef CONFIG_MEMORY_FAILURE
>> - ,atomic_long_read(&num_poisoned_pages) << (PAGE_SHIFT - 10)
>> + , atomic_long_read(&num_poisoned_pages) << (PAGE_SHIFT - 10)
>> #endif
>> #ifdef CONFIG_TRANSPARENT_HUGEPAGE
>> - ,K(global_page_state(NR_ANON_TRANSPARENT_HUGEPAGES) *
>> - HPAGE_PMD_NR)
>> + , K(global_page_state(NR_ANON_TRANSPARENT_HUGEPAGES) *
>> + HPAGE_PMD_NR)
>> +#endif
>
> Again, please don't include white space changes. They are confusing.
>
>> +#ifdef CONFIG_CMA
>> + , K(global_page_state(NR_FREE_CMA_PAGES))
>> #endif
>> );
>>
>> --
>> 2.0.0
>>
>>
>
--
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:[~2014-12-05 1:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 2:54 Xishi Qiu
2014-12-04 16:26 ` Michal Nazarewicz
2014-12-05 1:42 ` Xishi Qiu [this message]
2014-12-05 17:41 ` Michal Nazarewicz
2014-12-15 1:37 ` Xishi Qiu
2014-12-18 19:21 ` Michal Nazarewicz
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=54810D74.4030606@huawei.com \
--to=qiuxishi@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=mina86@mina86.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