From owner-freebsd-arch@FreeBSD.ORG Fri Apr 16 08:23:05 2010 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50132106566C; Fri, 16 Apr 2010 08:23:05 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 133A88FC1A; Fri, 16 Apr 2010 08:23:04 +0000 (UTC) Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id AE23090193; Fri, 16 Apr 2010 08:23:03 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.4/8.14.4) with ESMTP id o3G8N30A029918; Fri, 16 Apr 2010 08:23:03 GMT (envelope-from phk@critter.freebsd.dk) To: Attilio Rao From: "Poul-Henning Kamp" In-Reply-To: Your message of "Thu, 15 Apr 2010 12:10:21 +0200." Date: Fri, 16 Apr 2010 08:23:03 +0000 Message-ID: <29917.1271406183@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Giovanni Trematerra , freebsd-arch@freebsd.org Subject: Re: [PATCH] Syncer rewriting X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Apr 2010 08:23:05 -0000 In message , At tilio Rao writes: >The syncer, meant as what we have now, becames the 'standard one' but >switches to a different model. It becames per-mount and it then gets >rid of the syncer vnode. This also helps in simplifying a lot the >locking within the syncer because now any thread is responsible only >for its own dog-food. YeeeeEEEEEHAAAAA! Go! Go! GO! >- The standard syncer may be further improved getting rid of the >bufobj. It should actually handle a list of vnodes rather than a list >of bufobj. However similar optimizations may be done after the patch >is ready to enter the tree. That would be the wrong direction: we need the bufobj because for instance a RAID5 geom module does not have a vnode for the parity data. If you force the syncer to only work on vnodes, then we need a parallel mechanism for non-filesystem disk users. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.