From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 7 21:48:04 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE6DF16A4CE for ; Fri, 7 Nov 2003 21:48:04 -0800 (PST) Received: from pu.net (c-24-1-141-241.client.comcast.net [24.1.141.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC44A43FE9 for ; Fri, 7 Nov 2003 21:48:02 -0800 (PST) (envelope-from bugs@pu.net) Received: (from bugs@localhost) by pu.net (8.12.10/8.11.6) id hA85lsMx045036 for hackers@freebsd.org; Fri, 7 Nov 2003 23:47:55 -0600 (CST) (envelope-from bugs) From: Mark Hittinger Message-Id: <200311080547.hA85lsMx045036@pu.net> To: hackers@freebsd.org Date: Fri, 7 Nov 2003 23:47:51 -0600 (CST) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: re: sending messages, user process <--> kernel module X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Nov 2003 05:48:04 -0000 Another idea is to do something with msgsnd()/msgrcv() to allow the kernel to do interprocess communication with userland processes. Some of the older operating systems (DEC's TOPS-10, for example) used this technique. Later Mark Hittinger bugs@pu.net