From owner-freebsd-ports@FreeBSD.ORG Tue Nov 8 09:16:32 2005 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3940216A41F; Tue, 8 Nov 2005 09:16:32 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9834D43D45; Tue, 8 Nov 2005 09:16:26 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5F9B6.dip.t-dialin.net [84.165.249.182]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.1/8.13.1) with ESMTP id jA88s4ou073821; Tue, 8 Nov 2005 09:54:10 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from localhost (localhost [127.0.0.1]) by Andro-Beta.Leidinger.net (8.13.3/8.13.3) with ESMTP id jA89G97S003870; Tue, 8 Nov 2005 10:16:09 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by netchild.homeip.net (Horde MIME library) with HTTP; Tue, 08 Nov 2005 10:16:08 +0100 Message-ID: <20051108101608.2nucv3s9us4k844k@netchild.homeip.net> X-Priority: 3 (Normal) Date: Tue, 08 Nov 2005 10:16:08 +0100 From: Alexander Leidinger To: Ion-Mihai Tetcu References: <20051106.131413.122956532.yasu@utahime.org> <1131176568.3960.20.camel@shumai.marcuscom.com> <20051106.131413.122956532.yasu@utahime.org> <20051107111800.e199ndcxa8s0c444@netchild.homeip.net> <20051107122458.27a1f9e7@it.buh.tecnik93.com> <20051107145645.rav7hhtlsggk4sss@netchild.homeip.net> <20051107214458.30ca47f2@it.buh.tecnik93.com> In-Reply-To: <20051107214458.30ca47f2@it.buh.tecnik93.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.0.3) / FreeBSD-4.11 X-Virus-Scanned: by amavisd-new Cc: freebsd-ports@freebsd.org, le@freebsd.org, sos@freebsd.org Subject: Re: vinum, 5.x performance, ... (was: Re: ANNOUNCE: GNOME 2.12.1 has been merged into the ports tree) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2005 09:16:32 -0000 Ion-Mihai Tetcu wrote: > On Mon, 07 Nov 2005 14:56:45 +0100 > Alexander Leidinger wrote: > >> Ion-Mihai Tetcu wrote: >> >> > On Mon, 07 Nov 2005 11:18:00 +0100 >> > Alexander Leidinger wrote: >> > >> >> > - and performaces is a nightmare on atapi harddisks >> >> >> >> AFAIR 4.x enables the write cache (bad if there's a power failure >> >> in the soft-updates case, since without native command queueing the >> >> drivers may reorder writes witout the possibility to notify >> >> soft-updates about it), I' a little bit confused now. The man page says the WC is enabled by defaul= t, but I was under the impression, that it is disabled by default (I remember there was a discussion about this long ago). On my systems it is disabled, since I haven't removed the loader.conf line since the 4.x days. S=C3=B8ren= , is this a bug in the man page or did I got it wrong? >> > So on NCQ disks write_caching should be safe from consistency >> > point-of-view ? >> >> AFAIK: Enabling the write cache doesn't mean you use NCQ. So just >> because your drive is able to do NCQ, you shouldn't enable the write >> cache. If your controller, your disk and the OS is able to use NCQ, >> and you enable the use of NCQ, then everything is fine... assuming >> the drive doesn't lie to you. AFAIR there are or there where some >> drives which lie(d), but I don't remember the details. > > And finding out the what disk and controller use NCQ _and_ are > supported by our drivers can be done how ? Asking sos@FreeBSD.org (CCed) would be a way to find it out... At first I thought atacontrol tells you about it. But the "atacontrol cap ad0" command just tells you about the capabilities of the drive, not which of those capabilities are used by the driver (would be nice to have, specially in the light of seeing TCQ enabled but knowing that you said is doesn't work... at least with the previous implementation of ata). S=C3=B8ren, is there a way to en-/disable some of the capabilities with ata= control or something else? Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137 The debate rages on: Is PL/I Bachtrian or Dromedary?