Date: Fri, 22 Jun 2001 12:32:30 -0400 From: Bosko Milekic <bmilekic@technokratis.com> To: Alfred Perlstein <bright@sneakerz.org> Cc: freebsd-current@FreeBSD.ORG Subject: Re: [HEADS-UP]: Mbuf allocator changes Message-ID: <20010622123230.A749@technokratis.com> In-Reply-To: <20010622015201.W4543@sneakerz.org>; from bright@sneakerz.org on Fri, Jun 22, 2001 at 01:52:01AM -0500 References: <20010622024639.A40766@technokratis.com> <20010622015201.W4543@sneakerz.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 22, 2001 at 01:52:01AM -0500, Alfred Perlstein wrote: > If you want accurate stats you should be able to lock the per-cpu > stats areas all at once as long as you always do it in a certain > order, basically, lock CPU 0, then 1, then 2, then 3, sum then > unlock. If correctness doesn't matter you can just walk the > per cpu stats locking each (or not) and assumulating the info. I don't need to lock the per-CPU locks to merely read the stats (unless I'm reall obsessed with getting consistent stats at the cost of performance every time a person issues `netstat -m' or, even worse, runs `systat -mbufs'). The main issue with the mbtypes stats, as I've previously mentionned, was that it is difficult to *update* them consistently. However, I think I have devised a way. I'll keep you posted if you're interested in reviewing it. > -Alfred Cheers, -- Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010622123230.A749>