From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "song@kernel.org" <song@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"daniel@iogearbox.net" <daniel@iogearbox.net>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"hch@infradead.org" <hch@infradead.org>,
"ast@kernel.org" <ast@kernel.org>,
"rppt@kernel.org" <rppt@kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"andrii@kernel.org" <andrii@kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"mcgrof@kernel.org" <mcgrof@kernel.org>,
"imbrenda@linux.ibm.com" <imbrenda@linux.ibm.com>
Subject: Re: [PATCH v2 bpf 3/3] bpf: use vmalloc with VM_ALLOW_HUGE_VMAP for bpf_prog_pack
Date: Wed, 13 Apr 2022 15:51:46 +0000 [thread overview]
Message-ID: <7a14d025ea4de25d4989777f651d51117fc0a47c.camel@intel.com> (raw)
In-Reply-To: <CAPhsuW4pde5DTMNzRUHwPoxs6vh9AQPn+ny5-9cFVO4nVnYsGw@mail.gmail.com>
CC Mike, who has been working on a direct map fragmentation solution.
[0]
On Tue, 2022-04-12 at 14:00 -0700, Song Liu wrote:
> Since I am still learning the vmalloc/module_alloc code, I think I am
> not really capable of commenting on the direction. From our use
> cases, we do see performance hit due to large number of BPF
> program fragmenting the page table. Kernel module, OTOH, is not
> too big an issue for us, as we usually build hot modules into the
> kernel. That being said, we are interested in making the huge page
> interface general for BPF program and kernel module. We can
> commit resources to this effort.
That sounds great. Please feel free to loop me in if you do.
[0]
https://lore.kernel.org/lkml/20220127085608.306306-1-rppt@kernel.org/
prev parent reply other threads:[~2022-04-13 15:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220411233549.740157-1-song@kernel.org>
[not found] ` <20220411233549.740157-4-song@kernel.org>
2022-04-11 23:52 ` [PATCH v2 bpf 3/3] bpf: use module_alloc_huge for bpf_prog_pack Song Liu
[not found] ` <20220411233549.740157-2-song@kernel.org>
2022-04-12 4:18 ` [PATCH v2 bpf 1/3] vmalloc: replace VM_NO_HUGE_VMAP with VM_ALLOW_HUGE_VMAP Christoph Hellwig
2022-04-12 6:00 ` Song Liu
2022-04-21 2:24 ` Nicholas Piggin
2022-04-21 3:35 ` Nicholas Piggin
[not found] ` <20220411233549.740157-3-song@kernel.org>
2022-04-12 4:20 ` [PATCH v2 bpf 2/3] module: introduce module_alloc_huge Christoph Hellwig
2022-04-12 6:11 ` Song Liu
[not found] ` <20220411233549.740157-5-song@kernel.org>
2022-04-12 4:20 ` [PATCH v2 bpf 3/3] bpf: use vmalloc with VM_ALLOW_HUGE_VMAP for bpf_prog_pack Christoph Hellwig
2022-04-12 6:12 ` Song Liu
2022-04-12 17:20 ` Edgecombe, Rick P
2022-04-12 21:00 ` Song Liu
2022-04-13 15:51 ` Edgecombe, Rick P [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=7a14d025ea4de25d4989777f651d51117fc0a47c.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hch@infradead.org \
--cc=imbrenda@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=rppt@kernel.org \
--cc=song@kernel.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;
as well as URLs for NNTP newsgroup(s).