mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Leonid Shamis <leonid.shamis@gmail.com>
To: musl@lists.openwall.com
Subject: broadcast fd
Date: Tue, 15 Oct 2019 10:04:47 -0700	[thread overview]
Message-ID: <CAHSMefiLDxRJMFstWOysSmApqZeX296e1+uxhNVzL7SXjoLQdw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]

Hi Folks,

TLDR:

How do I broadcast a notification across processes, without a broker?

Long story:

I'm building an ipc-over-shm library with some unusual restrictions:
* There are multiple channels of communication (each in it's own shm).
* Each channel contains non-consumable resources (not a message queue).
* Multiple processes can produce resources on the same channel.
* Multiple consumers can access/use the resources.
* Resources are versioned and (some) old versions are kept available.
* Spurious wakeups are ok, but missing notifications (starvation) is not.
* The library must be robust (in the mutex sense), meaning a process may
crash without taking down the rest of the system.

I'm trying to figure out how to notify a process that a new resource is
available on a channel.

Right now, my library puts (the equivalent of) a robust conditional
variable in shared memory, for each channel.
Each process must spawn a thread per-channel, just to await the cv
broadcast.

I'd ideally like to use a single thread with something like an epoll.
For this, I'd need to get an fd (maybe eventfd) per channel into the hands
of every process that wants to connect to a channel.
fds, as I understand, cannot be shared via shared memory, only pipes, but
I'm required to be brokerless.
futex_fd are very deprecated.

Am I missing another approach?

Thanks,
--Leo

[-- Attachment #2: Type: text/html, Size: 1521 bytes --]

             reply	other threads:[~2019-10-15 17:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-15 17:04 Leonid Shamis [this message]
2019-10-19  1:44 ` Rich Felker

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=CAHSMefiLDxRJMFstWOysSmApqZeX296e1+uxhNVzL7SXjoLQdw@mail.gmail.com \
    --to=leonid.shamis@gmail.com \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).