From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: "Uttormark, Mike" <mike.uttormark@hpe.com>
Cc: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] Status of the RCU Red Black Tree
Date: Wed, 12 Jul 2023 15:36:28 -0400 [thread overview]
Message-ID: <ebcf5f74-347a-e94f-bc27-6f9f05fc3125@efficios.com> (raw)
In-Reply-To: <SJ0PR84MB2037002FA2B1C3C0C093E6959136A@SJ0PR84MB2037.NAMPRD84.PROD.OUTLOOK.COM>
On 7/12/23 14:44, Uttormark, Mike via lttng-dev wrote:
> What became of the red-black tree effort? I see it in the git repo, 10
> years old. It never made it onto master.
>
> What would it take to get it onto master and into a release branch?
Hi Mike,
There are a few things that are in the way of merging it into a liburcu
release, namely:
* An end user with a clearly defined use-case to allow defining a solid
API,
* Validation that those use-cases are not better covered by some
variation of my RCU Judy Array prototype instead, ref.:
https://github.com/urcu/userspace-rcu/tree/urcu/rcuja-simple-int
* More testing, both within the liburcu project and in terms of use of
the API from an application perspective,
* Funding for all that work, allowing us to prioritize this effort with
respect to our various other projects.
Thanks for your interest in the liburcu Red-Black Tree prototype! Please
don't hesitate to reach out to EfficiOS if HPE would like to explore
supporting this project.
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
prev parent reply other threads:[~2023-07-12 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 18:44 [lttng-dev] Status of the RCU Red Black Tree Uttormark, Mike via lttng-dev
2023-07-12 19:36 ` Mathieu Desnoyers via lttng-dev [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ebcf5f74-347a-e94f-bc27-6f9f05fc3125@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mike.uttormark@hpe.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).