linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Xin Hao <xhao@linux.alibaba.com>
To: willy@infradead.org
Cc: akpm@linux-foundation.org, adobriyan@gmail.com,
	keescook@chromium.org, xhao@linux.alibaba.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [RFC PATCH V4 0/1] mm: add last level page table numa info to /proc/pid/numa_pgtable
Date: Mon,  1 Aug 2022 20:17:26 +0800	[thread overview]
Message-ID: <20220801121727.76186-1-xhao@linux.alibaba.com> (raw)

In many data center servers, the shared memory architectures is
Non-Uniform Memory Access (NUMA), remote numa node data access
often brings a high latency problem, but what we are easy to ignore
is that the page table remote numa access, It can also leads to a
performance degradation.

So there add a new interface in /proc, This will help developers to
get more info about performance issues if they are caused by cross-NUMA.

V4 -> V3
1, Add some detects and spinlock when operating PMD page as Baolin Wang advised.

V2 -> V3
1, Fix compile warning bug.

V1 -> V2
1, As Matthew Wilcox advise, Simplify the code.
2, Do some codes format fix.

V3: https://lore.kernel.org/linux-mm/20220801032704.64356-1-xhao@linux.alibaba.com/
V2: https://lore.kernel.org/linux-mm/20220731155223.60238-1-xhao@linux.alibaba.com/
V1: https://lore.kernel.org/linux-mm/YuVqdcY8Ibib2LJa@casper.infradead.org/T/


Xin Hao (1):
  mm: add last level page table numa info to /proc/pid/numa_pgtable

 fs/proc/base.c     |  2 ++
 fs/proc/internal.h |  1 +
 fs/proc/task_mmu.c | 87 ++++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 90 insertions(+)

--
2.31.0


             reply	other threads:[~2022-08-01 12:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 12:17 Xin Hao [this message]
2022-08-01 12:17 ` [RFC PATCH V4 1/1] " Xin Hao
2022-08-01 13:28   ` David Hildenbrand
2022-08-04  8:04     ` haoxin
2022-08-04  8:12       ` David Hildenbrand
2022-08-04  9:30         ` haoxin

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=20220801121727.76186-1-xhao@linux.alibaba.com \
    --to=xhao@linux.alibaba.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=willy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox