From owner-freebsd-smp Mon Aug 17 11:12:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14493 for freebsd-smp-outgoing; Mon, 17 Aug 1998 11:12:57 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14479 for ; Mon, 17 Aug 1998 11:12:54 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id LAA15377; Mon, 17 Aug 1998 11:12:14 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpd015299; Mon Aug 17 11:12:04 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id LAA06500; Mon, 17 Aug 1998 11:12:00 -0700 (MST) From: Terry Lambert Message-Id: <199808171812.LAA06500@usr08.primenet.com> Subject: Re: Per processor load? To: Lars.Koeller@post.uni-bielefeld.de (Lars =?iso-8859-1?Q?K=F6ller?=) Date: Mon, 17 Aug 1998 18:12:00 +0000 (GMT) Cc: chuckr@glue.umd.edu, freebsd-smp@FreeBSD.ORG In-Reply-To: <199808170550.FAA27256@mitch.hrz.uni-bielefeld.de> from "Lars =?iso-8859-1?Q?K=F6ller?=" at Aug 17, 98 07:50:28 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > But thats only the first part of the problem! Where can I get > processor specific load information? I need to draw a separate load > graph for each CPU?? System load is based on number of processees in the ready-to-run state. For a symmetric system, if the load is 1.0 or above, both CPU's should be actively working. I suppose that what you are asking for is a "processor not idle in the case of 1.0 >= load >= 0.0". To get this, you would have to insert counters into the per CPU idle loops, probably using the Appendix H cycle counter before and after the per CPU HLT instruction, subtracting the count at exit of the last HLT from both, and then subtracting the entry from the exit, and dividing to get an "idle ratio". Gathering this type of statistic could be actively harmful to CPU latency coming out of the HLT condition, and could be as high as 10% to 20% of the systems ability to do work. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message