Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 9 Oct 2006 01:23:45 +0200
From:      "Attilio Rao" <attilio@freebsd.org>
To:        "Kip Macy" <kmacy@fsmware.com>,  "John-Mark Gurney" <gurney_j@resnet.uoregon.edu>,  "David Xu" <davidxu@freebsd.org>, freebsd-current@freebsd.org,  "Ivan Voras" <ivoras@fer.hr>
Subject:   Re: [PATCH] MAXCPU alterable in kernel config - needs testers
Message-ID:  <3bbf2fe10610081623l7f64651bya635f612273f730d@mail.gmail.com>
In-Reply-To: <20061008160742.N29803@demos.bsdclusters.com>
References:  <2fd864e0610080423q7ba6bdeal656a223e662a5d@mail.gmail.com> <20061008135031.G83537@demos.bsdclusters.com> <4529667D.8070108@fer.hr> <200610090634.31297.davidxu@freebsd.org> <20061008225150.GK793@funkthat.com> <3bbf2fe10610081555r67265368sf7f12edbf35bff0d@mail.gmail.com> <20061008155817.G29803@demos.bsdclusters.com> <3bbf2fe10610081603r1161ac38h4b679e452b6849f6@mail.gmail.com> <20061008160742.N29803@demos.bsdclusters.com>

next in thread | previous in thread | raw e-mail | index | archive | help
2006/10/9, Kip Macy <kmacy@fsmware.com>:
> In my own tree I have support for profiling all kernel locks (sx,
> lockmgr, spin mutexes, and blocking mutexes - not just the current
> profiling for blocking mutexes) which I'll commit after sun4v has
> been completely checked in.
>
> The biggest offenders on the workloads I've looked at are the
> lockmgr locks in VFS, user_map (sx) in VM, and sched_lock (spin).
>
> Substantial effort will be needed to make FreeBSD scale well past 4
> cpus.

Would you be interested in this:

perforce.freebsd.org://depot/user/attilio/attilio_smpng/...

Attilio


-- 
Peace can only be achieved by understanding - A. Einstein



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3bbf2fe10610081623l7f64651bya635f612273f730d>