From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <d0f55bf3d8e1e2b65e063fad7462756d@quanstro.net>
To: 9fans@9fans.net
From: erik quanstrom <quanstro@quanstro.net>
Date: Thu,  3 Jul 2008 20:26:11 -0400
In-Reply-To: <20080702154017.593D61E8C26@holo.morphisms.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] vx32 and 9vx performance, and on x86-64
Topicbox-Message-UUID: da7aa466-ead3-11e9-9d60-3106f5b1d025

> 	* the kprocdev framework.  all i/o into devip, devfs, and devdraw
> 	  is marshalled and handed off to a kproc running in a different
> 	  pthread, so that blocking i/o won't block the cpu0 pthread,
> 	  which is the only one that can run vx32.  this means that
> 	  all i/o gets copied one extra time inside the kernel.

why can only one thread run vx32?

- erik