unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers via Libc-alpha <libc-alpha@sourceware.org>
To: Eric Wong <normalperson@yhbt.net>, Carlos O'Donell <carlos@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [RFC/PoC] malloc: use wfcqueue to speed up remote frees
Date: Tue, 17 Jan 2023 14:05:34 -0500	[thread overview]
Message-ID: <d97c2927-4082-ce54-f45e-166d5835d308@efficios.com> (raw)
In-Reply-To: <20230117064251.M336757@dcvr>

On 2023-01-17 01:42, Eric Wong wrote:
> 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.

Hi Eric,

I'm very much interested to contribute portions of liburcu to glibc. I 
think what we would need at this point is to document where we see that 
liburcu infrastructure can improve glibc, and create a gradual 
integration roadmap based on priorities. We should identify the 
stake-holders interested in seeing this done, and then we can discuss 
the time-frame and resources available for this project.

That being said, I suspect we'd want to cover a few pieces of technology 
in this list, namely:

- Restartable Sequences (rseq system call),
- membarrier system call,
- liburcu and libside [1,2] RCU implementations,
- liburcu data structures (e.g. wfcqueue).

I would be tempted to go for an approach closer to the RCU 
implementation I have done in the libside project for glibc, because it 
supports having multiple RCU grace period domains per process, which 
allows to nicely split the locking dependencies into sub-domains, and 
therefore lessen the chances of deadlocks due to nesting of a 
global-domain RCU read-side/synchronize_rcu, and locking (e.g. mutexes).

Thanks,

Mathieu

[1] https://github.com/efficios/libside/blob/master/src/rcu.c
[2] https://github.com/efficios/libside/blob/master/src/rcu.h

-- 
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com


  reply	other threads:[~2023-01-17 19:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31  8:49 [RFC/PoC] malloc: use wfcqueue to speed up remote frees 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 via Libc-alpha
2023-01-17 19:05         ` Mathieu Desnoyers via Libc-alpha [this message]
2023-01-18 15:48           ` Mathieu Desnoyers via Libc-alpha
2023-01-18 19:12             ` Eric Wong via Libc-alpha
2023-01-18 19:17               ` Mathieu Desnoyers via Libc-alpha
2023-01-18 20:05                 ` Eric Wong via Libc-alpha
2023-01-18 14:53         ` Mathieu Desnoyers via Libc-alpha
2023-01-18 14:58           ` Mathieu Desnoyers via Libc-alpha
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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d97c2927-4082-ce54-f45e-166d5835d308@efficios.com \
    --to=libc-alpha@sourceware.org \
    --cc=carlos@redhat.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=normalperson@yhbt.net \
    /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).