From owner-freebsd-current@FreeBSD.ORG  Fri Mar  2 15:13:37 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
Delivered-To: freebsd-current@FreeBSD.ORG
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 98B0816A400
	for <current@freebsd.org>; Fri,  2 Mar 2007 15:13:37 +0000 (UTC)
	(envelope-from tinguely@casselton.net)
Received: from casselton.net (casselton.net [63.165.140.2])
	by mx1.freebsd.org (Postfix) with ESMTP id 48E9313C428
	for <current@freebsd.org>; Fri,  2 Mar 2007 15:13:37 +0000 (UTC)
	(envelope-from tinguely@casselton.net)
Received: from casselton.net (localhost [127.0.0.1])
	by casselton.net (8.13.8/8.13.8) with ESMTP id l22Eg6MZ058196
	for <current@freebsd.org>; Fri, 2 Mar 2007 08:42:06 -0600 (CST)
	(envelope-from tinguely@casselton.net)
Received: (from tinguely@localhost)
	by casselton.net (8.13.8/8.13.8/Submit) id l22Eg6QT058195
	for current@freebsd.org; Fri, 2 Mar 2007 08:42:06 -0600 (CST)
	(envelope-from tinguely)
Date: Fri, 2 Mar 2007 08:42:06 -0600 (CST)
From: Mark Tinguely <tinguely@casselton.net>
Message-Id: <200703021442.l22Eg6QT058195@casselton.net>
To: current@freebsd.org
Cc: 
Subject: multisegment bus_dmamem_alloc()
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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: Fri, 02 Mar 2007 15:13:37 -0000


Are there any other devices other than bktr(4) that could benefit
from a multisegment bus_dmamem_alloc(9) routine? The old USB system
comes to mind, but I have not studied the new USB. There may be others.

NetBSD only partially implements this (if the number page allocated > number
of segments, they punt and do a totally contiguous allocation - IMO, they
could fix this pretty easy though).

I know chages to contigmalloc() is a tricky subject. I was hoping
there are enough drivers that would provide enough merits to change
such an important part of the system. If not, please forgive this noise.

--Mark Tinguely