mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Question : Broadcast Inter Process Communication ?
Date: Fri, 17 May 2002 19:54:38 -0700	[thread overview]
Message-ID: <20020517195438.A30640@bougret.hpl.hp.com> (raw)
In-Reply-To: <20020517143052.A30047@bougret.hpl.hp.com> <E178uWc-0007mP-00@the-village.bc.nu>

On Sat, May 18, 2002 at 04:04:52AM +0100, Alan Cox wrote:
> > 	This "one sender - multiple reader" model seems common and
> > usefull enough that there must be a way to do that under Linux. I know
> > that it exist under Windows. Can somebody help me to find out how to
> > do it under Linux ?
> 
> Its actually a nontrivial construct - especially since readers can vanish
> and appear asynchronously during the lifetime of any event.

	That's exactly why I don't want to deal with it myself.
	However, the kernel deal with it all the time, and do it
well. For example RtNetlink event have this property (except that they
are kernel => process instead of beeing process => process).

> You could 
> implement it with multiple linked lists of pointers to refcounted objects,
> and you could do that in user space (eg with shared memory), the chances
> are that for all but the most extreme cases sending a copy of the event to
> each listener is cheaper, simpler and more debuggable

	Well, maybe I will simply use a UDP broadcast on the loopback,
it seems much simpler to me. I really wish there was broadcast Unix
sockets.

	Regards,

	Jean

  reply	other threads:[~2002-05-18  2:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-17 21:30 Jean Tourrilhes
2002-05-18  1:52 ` Olaf Dietsche
2002-05-18  1:57   ` Jean Tourrilhes
2002-05-18  3:04 ` Alan Cox
2002-05-18  2:54   ` Jean Tourrilhes [this message]
2002-05-18  3:23     ` Alan Cox
2002-05-20 17:03       ` Maksim (Max) Krasnyanskiy
2002-05-21  8:00         ` Peter Wächtler

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=20020517195438.A30640@bougret.hpl.hp.com \
    --to=jt@bougret.hpl.hp.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®