All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: prakash.sangappa@oracle.com
Cc: linux-kernel@vger.kernel.org, mhocko@kernel.org,
	dave.hansen@intel.com, cl@linux.com, khandual@linux.vnet.ibm.com
Subject: Re: [RFC PATCH] Add /proc/<pid>/numa_vamaps for numa node information
Date: Thu, 13 Sep 2018 02:02:12 +0300	[thread overview]
Message-ID: <20180912230212.GA6567@avx2> (raw)

> The /proc/pid/numa_vamaps shows mapped address ranges to numa node id
> from where the physical pages are allocated.

All these files make the problem with useless dentry and /proc/*/* inode
instantiations worse (unlike top level /proc/* files which are
tolerable).

> +address-range	numa-node-id
> +
> +00400000-00410000 N1
> +00410000-0047f000 N0
> +0047f000-00480000 N2
> +00480000-00481000 -
> +00481000-004a0000 N0
> +004a0000-004a2000 -
> +004a2000-004aa000 N2
> +004aa000-004ad000 N0
> +004ad000-004ae000 -

'N' is useless data.

Parsing with awk won't work because field #3 is separated with space
but field #2 with '-'.

%08lx-%08lx kind of sucks: 32-bit get aligned data so parsing can be
faster by pointing to &p[8+1] but not on 64-bit.
If scanf("%lx-%lx") is used then leading zeroes are useless.

Text is harder than it looks.
Please in the name of everything holy add new honest system call.

             reply	other threads:[~2018-09-12 23:02 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-12 23:02 Alexey Dobriyan [this message]
2018-09-13 22:17 ` [RFC PATCH] Add /proc/<pid>/numa_vamaps for numa node information prakash.sangappa
  -- strict thread matches above, loose matches on Subject: below --
2018-05-02  5:58 Prakash Sangappa
2018-05-02 21:33 ` Andrew Morton
2018-05-02 22:28   ` Dave Hansen
2018-05-02 23:17     ` prakash.sangappa
2018-05-03  8:46     ` Anshuman Khandual
2018-05-03 22:27       ` prakash.sangappa
2018-05-03 22:26         ` Dave Hansen
2018-05-07 23:22           ` prakash.sangappa
2018-05-08  0:05             ` Dave Hansen
2018-05-08  1:16               ` prakash.sangappa
2018-05-09 23:31                 ` Dave Hansen
2018-09-12 20:42                   ` prakash.sangappa
2018-09-12 20:57                     ` prakash.sangappa
2018-09-14  1:33                     ` Jann Horn
2018-09-14  6:21                       ` Michal Hocko
2018-09-14 12:49                         ` Jann Horn
2018-09-14 13:49                           ` Michal Hocko
2018-09-14 18:07                           ` Prakash Sangappa
2018-09-14 18:14                             ` Jann Horn
2018-05-02 23:43   ` prakash.sangappa
2018-05-03  8:57     ` Michal Hocko
2018-05-03 22:37       ` prakash.sangappa
2018-05-04 11:10         ` Michal Hocko
2018-05-03 18:03 ` Christopher Lameter
2018-05-03 22:39   ` prakash.sangappa
2018-05-04 11:12     ` Michal Hocko
2018-05-04 16:18       ` Prakash Sangappa
2018-05-04 16:18         ` Prakash Sangappa
2018-05-10  7:42         ` Michal Hocko
2018-05-10  7:42           ` Michal Hocko
2018-05-10 16:00           ` Prakash Sangappa
2018-05-10 16:00             ` Prakash Sangappa
2018-05-11  6:39             ` Michal Hocko
2018-05-04 14:57     ` Christopher Lameter
2018-05-04 16:27       ` Prakash Sangappa
2018-05-04 16:27         ` Prakash Sangappa
2018-05-07 14:47         ` Christopher Lameter
2018-05-07 14:47           ` Christopher Lameter
2018-05-07 22:50           ` prakash.sangappa
2018-05-08 12:53             ` Christopher Lameter

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=20180912230212.GA6567@avx2 \
    --to=adobriyan@gmail.com \
    --cc=cl@linux.com \
    --cc=dave.hansen@intel.com \
    --cc=khandual@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@kernel.org \
    --cc=prakash.sangappa@oracle.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.