From: Song Liu <song@kernel.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
mcgrof@kernel.org, peterz@infradead.org, tglx@linutronix.de,
x86@kernel.org
Subject: Re: [PATCH 0/3] Type aware module allocator
Date: Tue, 30 May 2023 15:37:24 -0700 [thread overview]
Message-ID: <CAPhsuW6g98Wz9Oj1NiwwZ1OkSVNXX10USByY0b9tEfzOt8SVQg@mail.gmail.com> (raw)
In-Reply-To: <20230529104530.GL4967@kernel.org>
On Mon, May 29, 2023 at 3:45 AM Mike Rapoport <rppt@kernel.org> wrote:
>
> On Sat, May 27, 2023 at 10:58:37PM -0700, Song Liu wrote:
> > On Sat, May 27, 2023 at 12:04 AM Kent Overstreet
> > <kent.overstreet@linux.dev> wrote:
> > >
> > > I think this needs to back to the drawing board and we need something
> > > simpler just targeted at executable memory; architecture specific
> > > options should definitely _not_ be part of the exposed interface.
> >
> > I don't think we are exposing architecture specific options to users.
> > Some layer need to handle arch specifics. If the new allocator is
> > built on top of module_alloc, module_alloc is handling that. If the new
> > allocator is to replace module_alloc, it needs to handle arch specifics.
>
> I'm for creating a new allocator that will replace module_alloc(). This
> will give us a clean abstraction that modules and all the rest will use and
> it will make easier to plug binpack or another allocator instead of
> vmalloc.
>
> Another point is with a new allocator we won't have weird dependencies on
> CONFIG_MODULE in e.g. bpf and kprobes.
>
> I'll have something ready to post as an RFC in a few days.
I guess this RFC is similar to unmapped_alloc()? If it replaces
vmalloc, we can probably trim this set down a bit (remove
mod_alloc_params and vmalloc_params, etc.).
Thanks,
Song
next prev parent reply other threads:[~2023-05-30 22:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 5:15 [PATCH 0/3] Type aware module allocator Song Liu
2023-05-26 5:15 ` [PATCH 1/3] module: Introduce module_alloc_type Song Liu
2023-05-26 6:07 ` Randy Dunlap
2023-05-26 22:29 ` Kent Overstreet
2023-05-26 23:09 ` Song Liu
2023-05-26 23:39 ` Kent Overstreet
2023-05-27 0:03 ` Song Liu
2023-05-27 3:19 ` Kent Overstreet
2023-05-27 6:00 ` Song Liu
2023-05-26 5:15 ` [PATCH 2/3] ftrace: Add swap_func to ftrace_process_locs() Song Liu
2023-05-26 5:15 ` [PATCH 3/3] x86/module: Use module_alloc_type Song Liu
2023-05-27 7:04 ` [PATCH 0/3] Type aware module allocator Kent Overstreet
2023-05-28 5:58 ` Song Liu
2023-05-29 10:45 ` Mike Rapoport
2023-05-30 22:37 ` Song Liu [this message]
2023-05-31 13:51 ` Mike Rapoport
2023-05-31 17:03 ` Song Liu
2023-05-31 19:54 ` Mike Rapoport
2023-05-29 18:25 ` Kent Overstreet
2023-05-30 22:48 ` Song Liu
2023-06-01 17:53 ` Kent Overstreet
2023-06-01 18:21 ` Kent Overstreet
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=CAPhsuW6g98Wz9Oj1NiwwZ1OkSVNXX10USByY0b9tEfzOt8SVQg@mail.gmail.com \
--to=song@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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 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.