From owner-freebsd-questions Sun Feb 18 9:28:21 2001 Delivered-To: freebsd-questions@freebsd.org Received: from p1.cs.ohiou.edu (p1.cs.ohiou.edu [132.235.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 129F037B491 for ; Sun, 18 Feb 2001 09:28:16 -0800 (PST) Received: from localhost (frussell@localhost) by p1.cs.ohiou.edu (8.9.3/8.9.3) with SMTP id MAA16208; Sun, 18 Feb 2001 12:28:10 -0500 (EST) Date: Sun, 18 Feb 2001 12:28:09 -0500 (EST) From: Russell Francis X-Sender: frussell@p1 To: Marco Masotti Cc: questions@FreeBSD.ORG Subject: Re: xcpustate and SMP In-Reply-To: <3A8F9B5B.8BE3C6FE@mclink.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To whom it may concern, Arun Sharma submitted a patch to the kernel and xosview that adds the correct data structures to the kernel to keep stats on a per cpu basis and to xosview to allow it to take advantage of the new stats. I can't find it on the PR database but you can get it from Unfortunately it is against the 4.0 kernel so . . . it may not be too useful. I used it as a basis to patch my 4.2-Release kernel by hand and it works great, and xosview has two independant cpu bars and the kernel booted, thanks Arun! :-) I would submit a new patch for 4.2 based off of his work if someone would tell me the proper way to do so without pissing people off. I am extremely new to FreeBSD and not quite sure of the file system structure or the proper way to submit patches etc. Thanks -Russ > Kent, my SMP config is actually a kernel SMP config. > > I believe Russel has got the right point when saying that something is missing > inside to admire the SMP at work. > Actually again, the SMP behaves quite right, the system appears quite fine grained > to allow most identical programs, when run in parallel, to run maxing all the > available cpus all their way out. That even if the specific applications are not > designed to accomodate their threads avoiding to step onto each other foot while > executing. > > I'm satisified with FreeBSD smp as I can be with linux, apparently as far as I've > seen till now. > > Yet, the problem is in xcpustate, and also possibly in xosview (not tried that > yet). > > Thank you for all replies. > > Regards all > > --- > Marco > > > > Kent Stewart wrote: > > > Russell Francis wrote: > > > > > > > > > > Marco Masotti wrote: > > > > > > > > > > Hello, > > > > > > > > > > I' running xcpustate on a bi-processor machine, but I'm not able to see > > > > > the two bars that would be involved in a SMP config. > > > > > > > > > > When running locally on supported multiprocessors > > > > > (SolbourneOS/MPsystems, Ultrix multiprocessors, Linux/SMP, and the > > > > > Gould NP1), there will be one bar for each CPU. > > > > > > > > > > My hardware is an Abit BP6 with 2xCeleron@550, FreeBSD 4._REL, xcpustate > > > > > is version 2.5, patchlevel 1.13 > > > > > > > > > > BTW, Is FreeBSD a *not supported* multiprocessor? > > > > > > > > It is unless you turn on multi-processor support in the kernel. > > > > > > > > Kent > > > > > > I am also running a dual system and even with SMP compiled into the > > > kernel, the issue with monitoring software (xcpustate, xosview) only > > > showing one CPU still exists. SMP is supported though because when > > > one processor is maxed out it will show 50% when both processors are > > > maxed it will show 100%. SMP works but the software to admire it isn't > > > quite there. > > > > That is too bad. I just got a Abit VP8 with dual 866 running and so > > far my AMD Thunderbird 900 will do buildworld's 20% faster. I was > > hoping there was something that would show me where the bottleneck > > was. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message