From: Eric Wong <normalperson@yhbt.net>
To: Carlos O'Donell <carlos@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [RFC/PoC] malloc: use wfcqueue to speed up remote frees
Date: Wed, 8 Aug 2018 10:40:50 +0000 [thread overview]
Message-ID: <20180808104050.b4jlm2gc4bgukqqc@dcvr> (raw)
In-Reply-To: <0cfdccea-d173-486c-85f4-27e285a30a1a@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?
Any ETA or update on urcu bundling? It's not urgent and I've
been busy with other projects, too; but it could be helpful for
planning around other work.
Anyways, I'm pretty satisfied at my original patch and will use
the __poll call in my next iteration. My main concern right now
is not hurting existing fast cases. So I will need to look into
more benchmarks on list archives and wiki...
Thanks.
prev parent reply other threads:[~2018-08-08 10:40 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
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 [this message]
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=20180808104050.b4jlm2gc4bgukqqc@dcvr \
--to=normalperson@yhbt.net \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.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).