From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 18 19:55:06 2005 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 067D916A4EC for ; Tue, 18 Jan 2005 19:55:06 +0000 (GMT) Received: from hotmail.com (bay15-f6.bay15.hotmail.com [65.54.185.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0E5043D49 for ; Tue, 18 Jan 2005 19:55:05 +0000 (GMT) (envelope-from street_chaman@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 18 Jan 2005 11:55:05 -0800 Message-ID: Received: from 82.254.52.43 by by15fd.bay15.hotmail.msn.com with HTTP; Tue, 18 Jan 2005 19:54:31 GMT X-Originating-IP: [82.254.52.43] X-Originating-Email: [street_chaman@hotmail.com] X-Sender: street_chaman@hotmail.com From: "Street Chaman" To: freebsd-hackers@freebsd.org Date: Tue, 18 Jan 2005 19:54:31 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed X-OriginalArrivalTime: 18 Jan 2005 19:55:05.0244 (UTC) FILETIME=[9AD02DC0:01C4FD97] Subject: Kernel mode programming -precisions 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: Tue, 18 Jan 2005 19:55:06 -0000 Thanks to everyone who read my question; here some precisions: Actually, my soft is a kind of interactive filter: it takes a lot of imput parameters (from keyboard at the moment, but as soon as i've understood how it works, i will increase the number of supported io devices); treats it in a particular way and produces an output. This 'particular way' requires a lot of clock cycle, so speed is my first problem; (that's part of reason why everything is directly written in assembly). I've already buffered input and output, but only as far at it was possible: since loop (X) input could affect loop (X-1) general data manipulation, and change output, it must be detected quickly. The time needed to read/write is still to long. When CPU is waiting on some new data, he cannot preform any other operation, and freezes data manipultion; that's why I'm looking for a new way to in/output the soft... I've found out in syscall.master the aio_read/write call. Man page says operation is asynchronous, so it returns quite immediatly after enqueuing the io thread. Could that be a solution ? Or back to kernel module (by the way: is it possible to write on in assembly) ? regards, Felix _________________________________________________________________ MSN Hotmail : antivirus et antispam intégrés http://www.msn.fr/newhotmail/Default.asp?Ath=f