On Sun, May 18, 2008 at 11:13 AM, Anselm R. Garbe <[EMAIL PROTECTED]> wrote: > On Sun, May 18, 2008 at 09:33:15AM +0200, Tuncer Ayaz wrote: >> and please don't forget to include: >> 1) BarOff >> and possibly an optimization in the case of BarOff which >> prevents any busy loop trying to read from stdin. > > Not sure who came up with claiming the stdin reader being a busy > loop. But the stdin reader has never been a busy loop in dwm, it > is select()-driven.
Noone came up with that claim, I'm just asking to be sure it's not without digging into the code. Sorry for the confusion. I should have been clearer. > The point why you might notice high loads is not because of dwm, > it is because your input feed produces high load (most likely > because you are using a sleep 1 based shell loop with lots of > processes being involved). I don't use the bar at all so dwm should be almost or entirely event driven and idle most of the time.
