All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Marczykowski <marmarek@invisiblethingslab.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	"Daniel Smith" <dpsmith@apertussolutions.com>,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Julien Grall" <julien@xen.org>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Anthony PERARD" <anthony.perard@vates.tech>,
	"Michal Orzel" <michal.orzel@amd.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH 2/3] x86/EFI: replace ebmalloc()
Date: Thu, 13 Nov 2025 14:01:44 +0100	[thread overview]
Message-ID: <aRXWucYrjiejVSKW@mail-itl> (raw)
In-Reply-To: <d027f21e-f2cc-4c63-9ebd-8f563d72c993@suse.com>

[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]

On Thu, Nov 13, 2025 at 01:53:40PM +0100, Jan Beulich wrote:
> On 13.11.2025 13:40, Marek Marczykowski wrote:
> > On Thu, Nov 13, 2025 at 12:09:37PM +0100, Jan Beulich wrote:
> >> Use the new brk_alloc() instead, with ebmalloc() merely being a thin
> >> wrapper.
> >>
> >> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> >> ---
> >> I'm not quite certain whether we ought to permit non-page-granular
> >> reservations. The in-memory image being somewhat larger due to possibly
> >> excessive padding isn't really a big problem, I think.
> > 
> > My grep says ebmalloc is used in just two places:
> > 1. For efi_memmap (via efi_arch_allocate_mmap_buffer())
> > 2. For various cmdline options and module names (via aplace_string())
> > 
> > The second one is probably undesirable to allocate full page for each
> > one. On the other hand, the current approach (putting small allocations
> > at the same page as an earlier page-aligned one) also has its issues -
> > see comments on 3/3 patch.
> 
> Imo if such sharing of a page is unwanted, then it's the side caring about
> the non-sharing which ought to request an exact multiple of pages. Wasting
> space due to doing this in the BRK implementation is undesirable.

Makes sense.

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2025-11-13 13:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13 11:06 [PATCH 0/3] x86: "brk" allocator Jan Beulich
2025-11-13 11:08 ` [PATCH 1/3] x86: introduce " Jan Beulich
2025-11-13 17:41   ` Marek Marczykowski-Górecki
2025-11-14  7:56     ` Jan Beulich
2025-11-13 11:09 ` [PATCH 2/3] x86/EFI: replace ebmalloc() Jan Beulich
2025-11-13 12:40   ` Marek Marczykowski
2025-11-13 12:46     ` Jan Beulich
2025-11-13 12:59       ` Marek Marczykowski
2025-11-13 13:24         ` Jan Beulich
2025-11-13 17:30           ` Marek Marczykowski
2025-11-13 12:53     ` Jan Beulich
2025-11-13 13:01       ` Marek Marczykowski [this message]
2025-11-13 11:10 ` [PATCH 3/3] xhci-dbc: use brk_alloc() Jan Beulich
2025-11-13 12:39   ` Marek Marczykowski
2025-11-13 12:50     ` Jan Beulich
2025-11-13 13:01       ` Marek Marczykowski
2025-11-13 15:29 ` [PATCH 0/3] x86: "brk" allocator Andrew Cooper

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=aRXWucYrjiejVSKW@mail-itl \
    --to=marmarek@invisiblethingslab.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=dpsmith@apertussolutions.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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.