From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Thu, 7 Apr 2011 16:19:06 -0400 To: 9fans@9fans.net Message-ID: In-Reply-To: <867hb5ygqt.fsf@cmarib.ramside> References: <86fwpz55nj.fsf@cmarib.ramside> <257867.782e4d7b.wsc0.mx@tumtum.plumbweb.net> <5ddd9deccbea5e8556dfc0c228b63311@ladd.quanstro.net> <86vcythf8h.fsf@cmarib.ramside> <86ipusd1wr.fsf@cmarib.ramside> <86zko3jt7n.fsf@cmarib.ramside> <867hb5ygqt.fsf@cmarib.ramside> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Busy mouse WAS: Re: Making read(1) an rc(1) builtin? Topicbox-Message-UUID: ce013c10-ead6-11e9-9d60-3106f5b1d025 > I don't have "*nomp=1" in plan9.ini, but I am running the 9atom kernel > you gave me. :) When it boots, it outputs the message "nomp: no mp > structure". i ran some actual tests, and it turns out that i can get 1515 interrupts/sec and 1950 syscalls/sec just by moving my usb mouse constantly. the load average is still 0, and the interrupt time is <= 3% so if you are seeing a performance problem just due to the mouse, the i would think that the fact that your machine is doing 8259-style interrupts has something to do with it. eio processing on 8259-style interrupts can take a long time. - erik