From owner-freebsd-current@FreeBSD.ORG Tue Aug 31 23:07:39 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F24201065679 for ; Tue, 31 Aug 2010 23:07:39 +0000 (UTC) (envelope-from andy@fud.org.nz) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id C63238FC12 for ; Tue, 31 Aug 2010 23:07:39 +0000 (UTC) Received: by iwn34 with SMTP id 34so293613iwn.13 for ; Tue, 31 Aug 2010 16:07:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.171.3 with SMTP id f3mr7250455ibz.145.1283296058895; Tue, 31 Aug 2010 16:07:38 -0700 (PDT) Sender: andy@fud.org.nz Received: by 10.231.141.100 with HTTP; Tue, 31 Aug 2010 16:07:38 -0700 (PDT) In-Reply-To: <236CEF13-3153-4ACA-9C67-B0116FF76EB3@FreeBSD.org> References: <236CEF13-3153-4ACA-9C67-B0116FF76EB3@FreeBSD.org> Date: Wed, 1 Sep 2010 11:07:38 +1200 X-Google-Sender-Auth: ruTCkhzUEiMt7aI37NRz7O5HsJ8 Message-ID: From: Andrew Thompson To: Rui Paulo Content-Type: text/plain; charset=ISO-8859-1 Cc: "current@freebsd.org Current" Subject: Re: DTrace userland project X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Aug 2010 23:07:40 -0000 On 1 September 2010 10:21, Rui Paulo wrote: > Hi, > The DTrace userland project is near completion and you can start using parts of it right away (only on FreeBSD HEAD right now). > > For more information on how to use DTrace with userland, please read: > http://wiki.freebsd.org/DTrace/userland > > This project is being sponsored by the FreeBSD Foundation. I am getting some odd behavior with your test example. Using your pid.d with the additional line "tick-1sec { exit(0); }" to limit it to one second runtime I get the following output CPU ID FUNCTION:NAME 1 45220 _sleep:entry 1 45220 _sleep:entry .... 0 45220 _sleep:entry With 54932 lines of output for the "_sleep:entry". It jumps around on the reported CPU, if I use cpuset to limit it to just one core then it does not reduce the 50,000 lines of output but just reports all on a single CPU. My kernel was build yesterday, r212042 Andrew