From owner-freebsd-current@FreeBSD.ORG Fri Apr 17 06:22:01 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 823CB106566C; Fri, 17 Apr 2009 06:22:01 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe10.tele2.se [212.247.155.33]) by mx1.freebsd.org (Postfix) with ESMTP id E1E498FC13; Fri, 17 Apr 2009 06:22:00 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=LvuvDqMzrUsA:10 a=jRiCUZqTDZ8A:10 a=j+k/Ze5hWUCaCztCgEjzDQ==:17 a=Ufx53kvaBBv-GnOLGPEA:9 a=LIekR4zw-QblQMPA7YSkbeVu7cIA:4 Received: from [81.191.55.181] (account mc467741@c2i.net HELO laptop) by mailfe10.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 1057704174; Fri, 17 Apr 2009 08:21:59 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Fri, 17 Apr 2009 08:24:31 +0200 User-Agent: KMail/1.9.7 References: <49BD117B.2080706@163.com> <200904161804.42399.jhb@freebsd.org> <49E7AC43.8050901@samsco.org> In-Reply-To: <49E7AC43.8050901@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200904170824.32184.hselasky@c2i.net> Cc: Richard Todd , Damian Gerow Subject: Re: ZFS checksum errors on umass(4) insertion X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2009 06:22:01 -0000 On Friday 17 April 2009, Scott Long wrote: > > It could, and if that's happening, then some proactive measures should > be taken by the usb code to generate buffers that won't bounce. It > would suck to have to go through the bounce code for every single > keystroke or mouse movement. I haven't looked at the new usb code, > though, and I thought that the old code did a contigmalloc of some > sort to avoid this. USB uses an alignment of 1-byte for its data buffers. It should only bounce when the page the data buffer is residing on is above 4GB. --HPS