From owner-svn-src-head@FreeBSD.ORG Sat Sep 5 06:16:52 2009 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 966FA106566B; Sat, 5 Sep 2009 06:16:52 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 234798FC0A; Sat, 5 Sep 2009 06:16:50 +0000 (UTC) Received: from [212.86.226.226] (account mav@alkar.net HELO mavbook.mavhome.dp.ua) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPSA id 253496099; Sat, 05 Sep 2009 09:16:47 +0300 Message-ID: <4AA20249.9000301@FreeBSD.org> Date: Sat, 05 Sep 2009 09:16:41 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20090901) MIME-Version: 1.0 To: John Baldwin References: <200909031237.n83CbIgk032551@svn.freebsd.org> <20090903114121.C20031@pooker.samsco.org> <9bbcef730909031245o7c380925sd29b2cc976c4d7dd@mail.gmail.com> <200909031602.01222.jhb@freebsd.org> In-Reply-To: <200909031602.01222.jhb@freebsd.org> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, Scott Long , src-committers@freebsd.org, Ivan Voras Subject: Re: svn commit: r196777 - head/sys/dev/ahci X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Sep 2009 06:16:52 -0000 John Baldwin wrote: > On Thursday 03 September 2009 3:45:07 pm Ivan Voras wrote: >> But ciss doesn't reference it at all so either it deviously assumes it >> or is independent of it. > > Actually, it may be much worse, it may be that the author of ciss(4) new that > ciss(4)'s largest supported I/O size was larger than 128k so they didn't > bother handling the limit at all giving the false impression the hardware has > no limit. In cases of ATA and CAM infrastructures it was is so, that if driver does not sets max_iosize or maxio respectively, it uses DFLTPHYS. So problem is only about non-ATA/CAM RAIDs or cases where wrong value could be specified explicitly. ciss(4) driver was explicitly limited to 64K, until somebody could review it's capabilities. -- Alexander Motin