From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <48099efcbb4d2fed33f6731aa0e206d9@quanstro.net>
References: <1251994812.16936.4807.camel@work.SFBay.Sun.COM>
	 <48099efcbb4d2fed33f6731aa0e206d9@quanstro.net>
Date: Thu,  3 Sep 2009 18:30:34 -0700
Message-ID: <dd6fe68a0909031830v399139cam870e6cbcedef4b53@mail.gmail.com>
Subject: Re: [9fans] "Blocks" in C
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Topicbox-Message-UUID: 637c3436-ead5-11e9-9d60-3106f5b1d025

> i'll grant you this in implementation. =C2=A0the pool library's lock
> in effect becomes plan 9's BLK. =C2=A0since the pool library is used
> in the kernel and user space, a user space application gets hit
> twice. =C2=A0i've been doing some full-tilt boogie testing with 2x10gbe
> and even with 2 cores, the BLK^wpool lock is devastating.

what does BLK stand for?

russ