From owner-freebsd-hackers Tue Oct 9 12:36:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from scaup.mail.pas.earthlink.net (scaup.mail.pas.earthlink.net [207.217.121.49]) by hub.freebsd.org (Postfix) with ESMTP id 08F7D37B409 for ; Tue, 9 Oct 2001 12:36:43 -0700 (PDT) Received: from mindspring.com (dialup-209.247.137.25.Dial1.SanJose1.Level3.net [209.247.137.25]) by scaup.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id MAA29329; Tue, 9 Oct 2001 12:36:40 -0700 (PDT) Message-ID: <3BC351FC.B98E3B02@mindspring.com> Date: Tue, 09 Oct 2001 12:37:32 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Matt Busigin Cc: freebsd-hackers@freebsd.org Subject: Re: Message Passing References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matt Busigin wrote: > For now, after looking at SVSV IPC, I am rewriting it so that the pointers > are in the proc struct, and I am initialising them in kern_exec.c, but I > am wishing/hoping there is a more elegant manner that I can do this > completely in modules. Look at the KNOTE() code that notes to the proc. This mechanism pretty much already exists, though no one has yet added support for SVR4 message queues (it should be trivial) or arbitrary messages (SVR4 shared memory or an mmaped file would end up being the best transport). Not to be a wet blanket, or anything -- I've often bemoaned the lack of this kind of thing in FreeBSD. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message