public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: DJ Delorie via Libc-alpha <libc-alpha@sourceware.org>
Cc: Zack Weinberg <zack@owlfolio.org>,  DJ Delorie <dj@redhat.com>
Subject: Re: [PATCH] malloc: Use correct C11 atomics for fastbin
Date: Mon, 12 Dec 2022 12:56:09 +0100	[thread overview]
Message-ID: <87r0x4suna.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <xnfsds5wty.fsf@greed.delorie.com> (DJ Delorie via Libc-alpha's message of "Tue, 06 Dec 2022 11:19:21 -0500")

* DJ Delorie via Libc-alpha:

> Zack Weinberg via Libc-alpha <libc-alpha@sourceware.org> writes:
>> Every time we start talking about fastbins vs tcache again I start 
>> wondering, again, what's stopping us from replacing the entire malloc 
>> implementation with jemalloc,
>
> There's a couple of things, but they're technical details, not political
> ones:
>
> * There's a copy of a "mini-malloc" in the dynamic loader that needs to
>   be somewhat compatible with the full copy in libc.so so that data
>   allocated in the loader can be used later.

This is not actually true, no compatibility is required.  We have manual
tracking for allocations and avoid freeing them with the wrong
allocator.  Otherwise interposed mallocs wouldn't work.

Thanks,
Florian


  parent reply	other threads:[~2022-12-12 11:56 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-21 16:09 Wilco Dijkstra
2022-11-21 16:18 ` Florian Weimer
2022-11-21 16:55   ` Wilco Dijkstra
2022-11-21 16:56     ` Wilco Dijkstra
2022-11-21 17:00     ` Florian Weimer
2022-12-02  5:11 ` DJ Delorie
2022-12-02  6:36   ` Florian Weimer
2022-12-02 10:56     ` Wilco Dijkstra
2022-12-02 11:24       ` Florian Weimer
2022-12-02 12:02         ` Wilco Dijkstra
2022-12-02 18:55           ` DJ Delorie
2022-12-05 18:39             ` Zack Weinberg
2022-12-06 16:19               ` DJ Delorie
2022-12-12  3:35                 ` Zack Weinberg
2022-12-12 11:57                   ` Florian Weimer
2022-12-12 11:56                 ` Florian Weimer [this message]
2022-12-06 13:29             ` Wilco Dijkstra
2022-12-06 13:37               ` Adhemerval Zanella Netto
2022-12-06 14:31                 ` Zack Weinberg
2022-12-06 16:23               ` DJ Delorie
2022-12-15 15:43                 ` Wilco Dijkstra
2022-12-02 18:55     ` DJ Delorie
2022-12-06 15:04 Wilco Dijkstra

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=87r0x4suna.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=dj@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=zack@owlfolio.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 read-only IMAP folder(s) and NNTP newsgroup(s).