public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jeff Adams" <jbadams@intensifi.com>
To: <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] What is the fastest mechanism for ipc communication under the gentoo-sources kernel
Date: Tue, 22 Jul 2003 10:07:41 -0700	[thread overview]
Message-ID: <FHEELGILKDENPLDMDNMJGEFODJAA.jbadams@intensifi.com> (raw)

Hello,

I have a producer process that makes updates to shared memory.  I need to
notify consumer processes (potentially multiple) as quickly as possible.

What I am looking for is a fast "wake-up" mechanism and a synchronization
mechanism so that events are not lost.

I'm currently using semaphores as the wake up mechanism.  Question is this
the fastest way to do this without going into a tight loop (waste of
processor cycles)?

I'd also have the issue of clients showing up asynchronously.  If I just use
semaphores counts based on the number of clients I run the risk of missing a
client.  Also if the clients process events too slowly then the producer
will keep incrementing the semaphore beyond the client count.  Then if one
client is faster than the others it may get awakened multiple times for the
same event.

Any suggestions?

Thanks in advance!




--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2003-07-22 17:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-22 17:07 Jeff Adams [this message]
2003-07-22 18:30 ` [gentoo-dev] What is the fastest mechanism for ipc communication under the gentoo-sources kernel Paul de Vrieze
2003-07-23  3:43   ` Dave Nellans
2003-07-23 14:13     ` wes chow

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=FHEELGILKDENPLDMDNMJGEFODJAA.jbadams@intensifi.com \
    --to=jbadams@intensifi.com \
    --cc=gentoo-dev@gentoo.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