linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mike Kravetz <mike.kravetz@oracle.com>
To: Hui Su <sh_def@163.com>,
	gregkh@linuxfoundation.org, rafael@kernel.org,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH] mm/hugetable.c: align some prints
Date: Mon, 26 Oct 2020 17:23:43 -0700	[thread overview]
Message-ID: <cf3e63c8-836c-1112-c7da-ae375ac43b65@oracle.com> (raw)
In-Reply-To: <20201009162359.GA19686@rlk>

On 10/9/20 9:23 AM, Hui Su wrote:
> in old code, it shows like:
> Node 0 ShmemHugePages:        0 kB
> Node 0 ShmemPmdMapped:        0 kB
> Node 0 FileHugePages:        0 kB
> Node 0 FilePmdMapped:        0 kB
> Node 0 HugePages_Total:     0
> Node 0 HugePages_Free:      0
> Node 0 HugePages_Surp:      0
> 
> which is not align. So we align it.
> 
> Signed-off-by: Hui Su <sh_def@163.com>

Apologies for the late reply.

I assume you you just want to make the output look better.  Correct?

To be honest, I am not sure about the policy for changing the output
of sysfs files.  My preference would be to not change the output.  Why?
When the output is changed there is always the possibility that someone
may have written code that depends on the current format.  It looks like
the output has been misaligned since the day the code was first written.

This code was recently changed to use sysfs_emit_at() instead of
sprintf().  At that time Greg noted that this also violates the sysfs
rule of one value per file.  So, it appears there may be a bigger issue
than alignment.

Greg,
Is it OK to break up these sysfs files to be one value per file if they
contained multiple values from day 1 of their existence?  I would prefer
not to touch them in case some is depending on current format.

-- 
Mike Kravetz

> ---
>  drivers/base/node.c | 4 ++--
>  mm/hugetlb.c        | 6 +++---
>  2 files changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/base/node.c b/drivers/base/node.c
> index 50af16e68d98..b5453c372c5b 100644
> --- a/drivers/base/node.c
> +++ b/drivers/base/node.c
> @@ -430,8 +430,8 @@ static ssize_t node_read_meminfo(struct device *dev,
>  		       "Node %d AnonHugePages:  %8lu kB\n"
>  		       "Node %d ShmemHugePages: %8lu kB\n"
>  		       "Node %d ShmemPmdMapped: %8lu kB\n"
> -		       "Node %d FileHugePages: %8lu kB\n"
> -		       "Node %d FilePmdMapped: %8lu kB\n"
> +		       "Node %d FileHugePages:  %8lu kB\n"
> +		       "Node %d FilePmdMapped:  %8lu kB\n"
>  #endif
>  			,
>  		       nid, K(node_page_state(pgdat, NR_FILE_DIRTY)),
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index 67fc6383995b..077860ea2452 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -3588,9 +3588,9 @@ int hugetlb_report_node_meminfo(int nid, char *buf)
>  	if (!hugepages_supported())
>  		return 0;
>  	return sprintf(buf,
> -		"Node %d HugePages_Total: %5u\n"
> -		"Node %d HugePages_Free:  %5u\n"
> -		"Node %d HugePages_Surp:  %5u\n",
> +		"Node %d HugePages_Total:%8u\n"
> +		"Node %d HugePages_Free: %8u\n"
> +		"Node %d HugePages_Surp: %8u\n",
>  		nid, h->nr_huge_pages_node[nid],
>  		nid, h->free_huge_pages_node[nid],
>  		nid, h->surplus_huge_pages_node[nid]);
> 


  reply	other threads:[~2020-10-27  0:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09 16:23 [PATCH] mm/hugetable.c: align some prints Hui Su
2020-10-27  0:23 ` Mike Kravetz [this message]
2020-10-27  6:14   ` Greg KH

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=cf3e63c8-836c-1112-c7da-ae375ac43b65@oracle.com \
    --to=mike.kravetz@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rafael@kernel.org \
    --cc=sh_def@163.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;
as well as URLs for NNTP newsgroup(s).