From owner-freebsd-virtualization@FreeBSD.ORG Sun Apr 27 10:55:48 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DA0C9884; Sun, 27 Apr 2014 10:55:48 +0000 (UTC) Received: from mail-la0-x233.google.com (mail-la0-x233.google.com [IPv6:2a00:1450:4010:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 301D9877; Sun, 27 Apr 2014 10:55:48 +0000 (UTC) Received: by mail-la0-f51.google.com with SMTP id gl10so677490lab.38 for ; Sun, 27 Apr 2014 03:55:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=lGzqBz0hT6BldItqxi4CbtDYKy5sspK+ccDgTEGZN8k=; b=V28zrsjAntd4J/NyULlE3VfPcShKjGN46CdO64W6EGITsFRUaQIcHhu6fl8Epy2N3Y DR9TKEsu6qUvU6D8JSZJwNEsOfsEuee2NFKif//vgmF948byrebJN6OoeKNjq09RzRzb Jydb6EQOVH0hCV+Qk2tN5RecrpN2iLJrqXoiWu7iHM/oTT0ViIIhEBMWhEKTo8xkq9oZ SSH+R92VJWUQclbGhYVLaeGghGzooDAPzu4xYzIqc5b8X0oCsdtbnRADb3P1j1L3CpUS WWBoE9yWIKUdd7gry4qFpA9dWHedQchAnwmbJc0K9aQ43+pjj38JU2RwPCDsY44W2V4n tquA== X-Received: by 10.112.85.6 with SMTP id d6mr13361331lbz.8.1398596145851; Sun, 27 Apr 2014 03:55:45 -0700 (PDT) Received: from kloomba ([95.104.135.172]) by mx.google.com with ESMTPSA id jm3sm14883484lbc.29.2014.04.27.03.55.44 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 27 Apr 2014 03:55:44 -0700 (PDT) Sender: Roman Bogorodskiy Date: Sun, 27 Apr 2014 14:55:03 +0400 From: Roman Bogorodskiy To: Peter Grehan Subject: Re: Understanding CPU and memory usage in Bhyve Message-ID: <20140427105502.GB7804@kloomba> References: <20140421102138.GA6157@kloomba> <535557BC.8030300@freebsd.org> <20140424160816.GB3494@kloomba> <535AB368.9060101@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="H8ygTp4AXg6deix2" Content-Disposition: inline In-Reply-To: <535AB368.9060101@freebsd.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-virtualization@FreeBSD.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Apr 2014 10:55:48 -0000 --H8ygTp4AXg6deix2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Peter Grehan wrote: > Hi Roman, >=20 > > But the summary is: is there a way to figure out how much CPU time > > bhyve and the guest spends on host CPUs N (N =3D 0, 1, ...)? >=20 > I don't think FreeBSD records that for a process, and bhyve doesn't=20 > record the guest vCPU time on individual host CPUs (it's an aggregate=20 > over all CPUs). >=20 > Do you know if Linux supports that ? As far as I understand, Linux supports that through Cgroups, specifically, quoting: http://docs.fedoraproject.org/en-US/Fedora/15/html/Resource_Management_Guid= e/sec-cpuacct.html cpuacct.usage_percpu reports the CPU time (in nanoseconds) consumed on each CPU by all tasks in this cgroup (including tasks lower in the hierarchy).=20 Roman Bogorodskiy --H8ygTp4AXg6deix2 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (FreeBSD) iQEcBAEBAgAGBQJTXOIGAAoJEMltX/4IwiJqpOsIAKxrX44phEjSKybFd6F+j/Lm GBUT4PHzDZPBJOKl/5+TRvxTZvfjNt/zIxjAZUr38QTzw5kxsRK9ekl4pWmE2IZj FDFOTxYGGPOpvaGtrUuzroJ4q9JUyUw3m9KYHCuLMcWYkvGulf3muGmtUNOIywJd KfmXqTrsLxFlXwq3UYEFF6pIprcTctyxS3BoL3zgRDCS4npJCLI1Z/bnEpZDhFY6 g/p3pFzSr6x9KVMsfXggGxxG628kKLDwC4GI2rfvUgnlMQ4neEzGzNURBJ9r/Ci4 XQG90ZYYHLAdOprPjSwKKlQlleZo/uh7mfm1sg2oAKo+NTDwcj4NOunesj4UroI= =+Me1 -----END PGP SIGNATURE----- --H8ygTp4AXg6deix2--