public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: Carlos O'Donell <carlos@redhat.com>
Cc: libc-alpha@sourceware.org,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [RFC/PoC] malloc: use wfcqueue to speed up remote frees
Date: Tue, 17 Jan 2023 06:42:51 +0000	[thread overview]
Message-ID: <20230117064251.M336757@dcvr> (raw)
In-Reply-To: <c061de55-cc2a-88fe-564b-2ea9c4a7e632@redhat.com>

Carlos O'Donell <carlos@redhat.com> wrote:
> >> - Adding urcu as a build-time dependency is not acceptable for
> >> bootstrap, instead we would bundle a copy of urcu and keep it
> >> in sync with upstream. Would that make your work easier?
>
> Eric Wong wrote:
> > Yes, bundling that sounds great.  I assume it's something for
> > you or one of the regular contributors to work on (build systems
> > scare me :x)
> 
> Yes, that is something we'd have to do.

Hi, bringing this topic from 2018 up again (+Cc Mathieu):
https://inbox.sourceware.org/libc-alpha/c061de55-cc2a-88fe-564b-2ea9c4a7e632@redhat.com/T/

I'm wondering if URCU-in-glibc is still on the table.  I'm also
considering an learning C11 atomics and deriving a standalone
wfcqueue w/o URCU atomics.

Thanks.

  parent reply	other threads:[~2023-01-17  6:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31  8:49 Eric Wong
2018-07-31 12:16 ` Carlos O'Donell
2018-07-31 23:18   ` Eric Wong
2018-08-01  4:41     ` Carlos O'Donell
2018-08-01  6:23       ` Eric Wong
2018-08-01  7:01         ` Carlos O'Donell
2018-08-01  9:26           ` Eric Wong
2018-08-02 21:38             ` Carlos O'Donell
2023-01-17  6:42       ` Eric Wong [this message]
2023-01-17 19:05         ` Mathieu Desnoyers
2023-01-18 15:48           ` Mathieu Desnoyers
2023-01-18 19:12             ` Eric Wong
2023-01-18 19:17               ` Mathieu Desnoyers
2023-01-18 20:05                 ` Eric Wong
2023-01-18 14:53         ` Mathieu Desnoyers
2023-01-18 14:58           ` Mathieu Desnoyers
2018-08-08 10:40   ` Eric Wong

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=20230117064251.M336757@dcvr \
    --to=normalperson@yhbt.net \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=mathieu.desnoyers@efficios.com \
    /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).