From owner-freebsd-fs@FreeBSD.ORG Wed Aug 31 08:11:06 2011 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BCB40106566C; Wed, 31 Aug 2011 08:11:06 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 828D78FC15; Wed, 31 Aug 2011 08:11:06 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:6407:f3f9:7d93:d34c]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 4DDB34AC31; Wed, 31 Aug 2011 12:11:05 +0400 (MSD) Date: Wed, 31 Aug 2011 12:11:02 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <170569583.20110831121102@serebryakov.spb.ru> To: Kirk McKusick In-Reply-To: <201108302300.p7UN0jJ6022811@chez.mckusick.com> References: <1693072185.20110831022933@serebryakov.spb.ru> <201108302300.p7UN0jJ6022811@chez.mckusick.com> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@FreeBSD.org, lev@FreeBSD.org Subject: Re: Very inconsistent (read) speed on UFS2 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 08:11:06 -0000 Hello, Kirk. You wrote 31 =E0=E2=E3=F3=F1=F2=E0 2011 =E3., 3:00:45: > So, my new theory on why your O_DIRECT test is running slowly is due > to the single threading in the GEOM layer. Pawel Jakub Dawidek (pjd@) > gave a very interesting talk on this problem at this year's BSDCan. I want to stress my point: it is not low speed, what especially bother me. It is inconsistency. Bad drive, always-single-threaded-GEOM, etc., should give consistent slow speed. Bad code in geom_raid5 could give inconsistent write speed, du to caching, but reading path is as straight and simple as possible here. Bad drive or AST-GEOM is not what simple to fix (ok, bad drive IS simple to replace, of course). But I suspect, that here is some simple "misunderstanding" between geom_raid5 code and VFS/FFS2 layer, which I could fix. But I don't know where to look at. --=20 // Black Lion AKA Lev Serebryakov