From owner-freebsd-alpha Tue Nov 27 3:18:13 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from asterix.fh-schmalkalden.de (asterix.fh-schmalkalden.de [194.94.30.50]) by hub.freebsd.org (Postfix) with ESMTP id 44D3D37B419 for ; Tue, 27 Nov 2001 03:18:06 -0800 (PST) Received: from yahoo.de (iwgraf18.informatik.fh-schmalkalden.de [194.94.28.198]) by asterix.fh-schmalkalden.de (8.9.0/8.9.0) with ESMTP id MAA11161 for ; Tue, 27 Nov 2001 12:18:03 +0100 (MET) Message-ID: <3C03741A.55375021@yahoo.de> Date: Tue, 27 Nov 2001 12:08:10 +0100 From: Falko Meyer Organization: FH Schmalkalden/Germany, dep. of computer science X-Mailer: Mozilla 4.7C-SGI [en] (X11; I; IRIX 6.5 IP32) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-alpha@freebsd.org Subject: Re: mprotect() takes quite long -- anyone knows this? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello! I've got the same machine and have the same effects, I think. A terrible example is vim, which needs some seconds to start. It was the same with FreeBSD 4.2-RELEASE too. I haven't investigated it like you, but with a previously installed RedHat 6.2 I noticed that a hdparm -T (which measures the filebuffer-speed) i had 10MB/s or something near that. I think that this is a very slow memory performance, which may have something to do with that. I think this can't be defective memory because this machine uses ECC-RAM and you would see massive ECC-errors in this case. MfG Falko Meyer >Moin, > >I run FreeBSD 4.4-RELEASE on an AXPpci33 board with 64MB of RAM. It runs >quite stable, but dead slow when executing commands. After a process is >running, it seems to work at normal speed (haven't really verified this, >though). > >Investigation shows that most of the time is used up in an mprotect() system >call: > > >-=======================================================================- > >74[thiemo@myg:~]> time w > 1:15PM up 2 days, 12:16, 1 user, load averages: 0.04, 0.07, 0.02 > USER TTY FROM LOGIN@ IDLE WHAT > thiemo p0 somewhere 11:28AM - w > 0.882u 0.094s 0:00.99 97.9% 29+199k 0+0io 0pf+0w > >then, from a "ktrace w": > >77[thiemo@myg:~]> kdump -R | grep mprotect > 52860 w 0.004988 CALL mprotect(0x160062000,0xc2000,0x7) > 52860 w 0.000581 RET mprotect 0 > 52860 w 0.865540 CALL mprotect(0x160062000,0xc2000,0x5) > 52860 w 0.001066 RET mprotect 0 > >-=======================================================================- > >Isn't this a bit long for a syscall? What's going on here? Defective memory? >Other flaws? Just me being too impatioent? A week ago, the Alpha ran just >fine under OpenBSD 2.3 (old and bah) -- but I want to make it running >FreeBSD as well... > >If you need more information, contact me, please -- and thanks for any >hints! > >Cheers, > Thiemo > > >-- >Thiemo Nordenholz http://www.thiemo.net >"Computers are great at wasting time that would be otherwise be difficult to >waste." -- Cliff Stoll > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-alpha" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message