> Im not sure this is true. It will happily schedule threads without a > timer interupt, but it will not time slice threads which are running > with the same priority. In many systems you don't actually need time > slicing. You're right, by kernel I assumed the default mlqueue timeslicing scheduler, not the bitmap one which might not need a timer.