linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Andrii Nakryiko <andrii@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, brauner@kernel.org,
	viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org,
	bpf@vger.kernel.org, gregkh@linuxfoundation.org,
	linux-mm@kvack.org, liam.howlett@oracle.com, surenb@google.com,
	rppt@kernel.org, Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: [PATCH v4 0/7] ioctl()-based API to query VMAs from /proc/<pid>/maps
Date: Tue, 11 Jun 2024 11:59:50 -0700	[thread overview]
Message-ID: <20240611115950.35197b36eafe0a804ecaa0de@linux-foundation.org> (raw)
In-Reply-To: <20240611110058.3444968-1-andrii@kernel.org>


(Please cc Alexey on procfs changes)

On Tue, 11 Jun 2024 04:00:48 -0700 Andrii Nakryiko <andrii@kernel.org> wrote:

> Implement binary ioctl()-based interface to /proc/<pid>/maps file to allow
> applications to query VMA information more efficiently than reading *all* VMAs
> nonselectively through text-based interface of /proc/<pid>/maps file.

Looks nice but I'll await further reviewer input.

> 
> ...
>
>  Documentation/filesystems/proc.rst          |   9 +
>  fs/proc/task_mmu.c                          | 366 +++++++++++--
>  include/uapi/linux/fs.h                     | 156 +++++-
>  tools/include/uapi/linux/fs.h               | 550 ++++++++++++++++++++
>  tools/testing/selftests/bpf/.gitignore      |   1 +
>  tools/testing/selftests/bpf/Makefile        |   2 +-
>  tools/testing/selftests/bpf/procfs_query.c  | 386 ++++++++++++++
>  tools/testing/selftests/bpf/test_progs.c    |   3 +
>  tools/testing/selftests/bpf/test_progs.h    |   2 +
>  tools/testing/selftests/bpf/trace_helpers.c | 104 +++-
>  10 files changed, 1508 insertions(+), 71 deletions(-)
>  create mode 100644 tools/include/uapi/linux/fs.h
>  create mode 100644 tools/testing/selftests/bpf/procfs_query.c

Should the selftests be under bpf/?  This is a procfs feature which
could be used by many things apart from bpf and it really isn't a bpf
thing at all.  Wouldn't tools/testing/selftests/proc/ be a more
appropriate place?



  parent reply	other threads:[~2024-06-11 18:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11 11:00 Andrii Nakryiko
2024-06-11 11:00 ` [PATCH v4 1/7] fs/procfs: extract logic for getting VMA name constituents Andrii Nakryiko
2024-06-11 11:00 ` [PATCH v4 2/7] fs/procfs: implement efficient VMA querying API for /proc/<pid>/maps Andrii Nakryiko
2024-06-11 11:00 ` [PATCH v4 3/7] fs/procfs: add build ID fetching to PROCMAP_QUERY API Andrii Nakryiko
2024-06-12 18:28   ` Liam R. Howlett
2024-06-17 20:38     ` Andrii Nakryiko
2024-06-11 11:00 ` [PATCH v4 4/7] docs/procfs: call out ioctl()-based PROCMAP_QUERY command existence Andrii Nakryiko
2024-06-11 11:00 ` [PATCH v4 5/7] tools: sync uapi/linux/fs.h header into tools subdir Andrii Nakryiko
2024-06-11 11:00 ` [PATCH v4 6/7] selftests/bpf: make use of PROCMAP_QUERY ioctl if available Andrii Nakryiko
2024-06-11 11:00 ` [PATCH v4 7/7] selftests/bpf: add simple benchmark tool for /proc/<pid>/maps APIs Andrii Nakryiko
2024-06-11 18:59 ` Andrew Morton [this message]
2024-06-12  6:57   ` [PATCH v4 0/7] ioctl()-based API to query VMAs from /proc/<pid>/maps Andrii Nakryiko

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=20240611115950.35197b36eafe0a804ecaa0de@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=adobriyan@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=brauner@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=liam.howlett@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rppt@kernel.org \
    --cc=surenb@google.com \
    --cc=viro@zeniv.linux.org.uk \
    /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