All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yafang Shao <laoar.shao@gmail.com>
To: cl@linux.com, penberg@kernel.org, rientjes@google.com,
	iamjoonsoo.kim@lge.com, akpm@linux-foundation.org,
	willy@infradead.org, hannes@cmpxchg.org, mhocko@suse.com,
	david@redhat.com, osalvador@suse.de, linmiaohe@huawei.com,
	steven.price@arm.com, guro@fb.com,
	alexander.h.duyck@linux.intel.com, ying.huang@intel.com
Cc: linux-mm@kvack.org, Yafang Shao <laoar.shao@gmail.com>
Subject: [PATCH 0/2] mm: improve the output of print_page_info()
Date: Fri, 15 Jan 2021 14:13:47 +0800	[thread overview]
Message-ID: <20210115061349.67386-1-laoar.shao@gmail.com> (raw)

Before that patchset, the output of print_page_info() is
[ 6155.716018] INFO: Slab 0x000000004027dd4f objects=33 used=3 fp=0x000000008cd1579c flags=0x17ffffc0010200

While after it, the output is
[ 8843.757770] INFO: Slab 0x00000000f0e98335 objects=33 used=3 fp=0x00000000b643c7d8 flags=0x10200(slab|head)

The new one is more friendly and human readable.

Yafang Shao (2):
  mm, slub: use pGp to print page flags
  mm: introduce PAGE_FLAGS() to make output of page flags better

 include/linux/page-flags.h | 2 ++
 mm/slub.c                  | 5 +++--
 2 files changed, 5 insertions(+), 2 deletions(-)

-- 
1.8.3.1



             reply	other threads:[~2021-01-15  6:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15  6:13 Yafang Shao [this message]
2021-01-15  6:13 ` [PATCH 1/2] mm, slub: use pGp to print page flags Yafang Shao
2021-01-15  8:46   ` David Hildenbrand
2021-01-15 10:14     ` Yafang Shao
2021-01-15  6:13 ` [PATCH 2/2] mm: introduce PAGE_FLAGS() to make output of page flags better Yafang Shao
2021-01-15  8:39   ` David Hildenbrand
2021-01-15 10:10     ` Yafang Shao
2021-01-15 10:15       ` David Hildenbrand
2021-01-15 10:17         ` Yafang Shao

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=20210115061349.67386-1-laoar.shao@gmail.com \
    --to=laoar.shao@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.h.duyck@linux.intel.com \
    --cc=cl@linux.com \
    --cc=david@redhat.com \
    --cc=guro@fb.com \
    --cc=hannes@cmpxchg.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=osalvador@suse.de \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.com \
    --cc=steven.price@arm.com \
    --cc=willy@infradead.org \
    --cc=ying.huang@intel.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 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.