Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262683AbTHUPOg (ORCPT ); Thu, 21 Aug 2003 11:14:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262739AbTHUPOf (ORCPT ); Thu, 21 Aug 2003 11:14:35 -0400 Received: from chaos.analogic.com ([204.178.40.224]:4992 "EHLO chaos.analogic.com") by vger.kernel.org with ESMTP id S262683AbTHUPOd (ORCPT ); Thu, 21 Aug 2003 11:14:33 -0400 Date: Thu, 21 Aug 2003 11:14:45 -0400 (EDT) From: "Richard B. Johnson" X-X-Sender: root@chaos Reply-To: root@chaos.analogic.com To: Pankaj Garg cc: Linux kernel Subject: Re: Messaging between kernel modules and User Apps In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 952 Lines: 30 On Thu, 21 Aug 2003, Pankaj Garg wrote: > Hi, > > I am writing a kernel module. The module will need to send asynchronous > messages to a User Application. Is there a good and efficient way of > doing this? > > > Thanks, > Pankaj > The de facto standard for network devices is to use sockets. For character and and block devices Unix/Linux uses the open/poll/ioctl/read mechanisms. Some Linux drivers use the /proc file-system for 'information'. You could send your module a pid via proc and have it send a signal to your application as a result of an event. Cheers, Dick Johnson Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips). Note 96.31% of all statistics are fiction. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/