From owner-freebsd-current@FreeBSD.ORG  Thu Jul  8 09:35:44 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E6C8116A4CF
	for <current@FreeBSD.org>; Thu,  8 Jul 2004 09:35:44 +0000 (GMT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3AA9F43D1F
	for <current@FreeBSD.org>; Thu,  8 Jul 2004 09:35:44 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i689ZW9m011366;
	Thu, 8 Jul 2004 11:35:33 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: ticso@cicely.de
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Thu, 08 Jul 2004 11:31:46 +0200."
             <20040708093145.GX12877@cicely12.cicely.de> 
Date: Thu, 08 Jul 2004 11:35:32 +0200
Message-ID: <11354.1089279332@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
cc: mycroft@netbsd.org
cc: Julian Elischer <julian@elischer.org>
cc: "M. Warner Losh" <imp@bsdimp.com>
cc: current@FreeBSD.org
Subject: Re: speeding up ugen by an order of magnitude. 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jul 2004 09:35:45 -0000

In message <20040708093145.GX12877@cicely12.cicely.de>, Bernd Walter writes:

>Can we do interleaving with physio?

physio is just a way to avoid copyin/copyout.  It maps & pins the
space the user indicated in read(2) or write(2) into the kernel
address space so that the kernel can access it directly.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.