From owner-freebsd-arm@FreeBSD.ORG Fri Aug 8 17:36:54 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2B7C5EF9 for ; Fri, 8 Aug 2014 17:36:54 +0000 (UTC) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E1D942171 for ; Fri, 8 Aug 2014 17:36:53 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1XFo5s-0007IB-Ce for freebsd-arm@freebsd.org; Fri, 08 Aug 2014 19:36:44 +0200 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: freebsd-arm@freebsd.org Subject: Re: testing new pmap code References: <53CFE285.9040101@rice.edu> Date: Fri, 08 Aug 2014 19:36:43 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <53CFE285.9040101@rice.edu> User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.3.2 X-Scan-Signature: ba572e8a3bde05b4b19613c12a9e49fc X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Aug 2014 17:36:54 -0000 On Wed, 23 Jul 2014 18:27:49 +0200, Alan Cox wrote: > Folks, > > About a week ago I committed some new pmap code on all architectures, > including arm. However, that code isn't "active" until the attached > patch is committed. Before I commit this patch, I'd like to ask people > to test it on arm "classic" and especially v6. (The v6 pmap changes > were more complicated.) > > Here is how to test it. Before you apply the kernel patch, compile and > run the attached program, mlockall2A.c, in a loop. Something like this: > > # while ( 1 ) > while? ./mlockall2A > while? sysctl vm.stats.vm.v_wire_count > while? sleep 7 > while? end > > You should see the wire count steadily increase, because there is a > wired page leak. > > Now, apply the kernel patch, and repeat the same test. This time, the > wire count should stabilize. > > If you're testing on arm v6, substitute > > sysctl vm.stats.vm.v_wire_count vm.pmap.section > > for > > sysctl vm.stats.vm.v_wire_count > > so that I can verify that we're handling superpages correctly. > > Thanks, > Alan > I setup my Sheevaplug (armv5?) with 11-CURRENT. Does this need testing still? I saw that the patch is already committed. And running the test does not crash my machine. The v_wire_count goes up, seems to stabilize and after I stop the loop it goes down again. Ronald.