bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Song Liu <songliubraving@fb.com>
Cc: bpf <bpf@vger.kernel.org>,
	Network Development <netdev@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Kernel Team <kernel-team@fb.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v7 bpf-next 0/3] introduce bpf_iter for task_vma
Date: Fri, 12 Feb 2021 13:04:56 -0800	[thread overview]
Message-ID: <CAADnVQKz8fzvVfqozE2QePjXk4bG8gyTow8Nm+CRYcWM7pf6DA@mail.gmail.com> (raw)
In-Reply-To: <20210212183107.50963-1-songliubraving@fb.com>

On Fri, Feb 12, 2021 at 10:31 AM Song Liu <songliubraving@fb.com> wrote:
>
> This set introduces bpf_iter for task_vma, which can be used to generate
> information similar to /proc/pid/maps. Patch 4/4 adds an example that
> mimics /proc/pid/maps.
>
> Current /proc/<pid>/maps and /proc/<pid>/smaps provide information of
> vma's of a process. However, these information are not flexible enough to
> cover all use cases. For example, if a vma cover mixed 2MB pages and 4kB
> pages (x86_64), there is no easy way to tell which address ranges are
> backed by 2MB pages. task_vma solves the problem by enabling the user to
> generate customize information based on the vma (and vma->vm_mm,
> vma->vm_file, etc.).
>
> Changes v6 => v7:
>   1. Let BPF iter program use bpf_d_path without specifying sleepable.
>      (Alexei)

Applied. Thanks!

      parent reply	other threads:[~2021-02-12 21:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12 18:31 Song Liu
2021-02-12 18:31 ` [PATCH v7 bpf-next 1/3] bpf: introduce task_vma bpf_iter Song Liu
2021-02-12 18:31 ` [PATCH v7 bpf-next 2/3] bpf: allow bpf_d_path in bpf_iter program Song Liu
2021-02-12 18:31 ` [PATCH v7 bpf-next 3/3] selftests/bpf: add test for bpf_iter_task_vma Song Liu
2021-02-12 21:04 ` Alexei Starovoitov [this message]

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=CAADnVQKz8fzvVfqozE2QePjXk4bG8gyTow8Nm+CRYcWM7pf6DA@mail.gmail.com \
    --to=alexei.starovoitov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@fb.com \
    --cc=linux-mm@kvack.org \
    --cc=netdev@vger.kernel.org \
    --cc=songliubraving@fb.com \
    --subject='Re: [PATCH v7 bpf-next 0/3] introduce bpf_iter for task_vma' \
    /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

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).