Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261800AbVCSVIU (ORCPT ); Sat, 19 Mar 2005 16:08:20 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261804AbVCSVIU (ORCPT ); Sat, 19 Mar 2005 16:08:20 -0500 Received: from linux01.gwdg.de ([134.76.13.21]:52427 "EHLO linux01.gwdg.de") by vger.kernel.org with ESMTP id S261800AbVCSVIS (ORCPT ); Sat, 19 Mar 2005 16:08:18 -0500 Date: Sat, 19 Mar 2005 22:08:13 +0100 (MET) From: Jan Engelhardt To: Karim Yaghmour cc: linux-kernel@vger.kernel.org Subject: Re: Relayfs question In-Reply-To: <423C913B.6000307@opersys.com> Message-ID: References: <423C78E8.3040200@ev-en.org> <423C913B.6000307@opersys.com> 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: 1160 Lines: 30 >> Ok, urandom was a bad example. I have my tty logger (ttyrpld.sf.net) which >> moves a lot of data (depends) to userspace. It uses a ring buffer [...] >[...] >Basically, all the transport code you are doing in the kernel side of >your logger would be taken care of by relayfs. And given that there are >a lot of people doing similar ad-hoc buffering code, it just makes >sense to have one well-tested yet generic mechanism. Have a look at >Documentation/filesystems/relayfs.txt for the API details. Well, what about things like urandom? It also moves "a lot" of data and does nothing else. >[...] >Just to avoid any confusion, note that I'm referring mainly to rpldev.c, >which is the kernel-side driver for the logger, I haven't looked at any >of the user tools. The userspace daemon just read()s the device and analyzes it. Nothing to optimize there, with respect to relayfs, I think. Jan Engelhardt -- - 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/