On Monday 19 June 2006 21:54, Jan Engelhardt wrote:
> >Were you running them SCHED_IDLEPRIO or in compute mode? They would do
> > that.
>
> I have not changed anything, so I presume SCHED_NORMAL.
> Unless they have been made SCHED_IDLEPRIO/compute by staircase's logic...
No it wouldn't do that.
I've not seen what you describe happening but definitely the timing of
parallelising jobs in 'make' completely changes with cpu scheduler changes
and with I/O scheduler changes.
However if it's purely unrelated cpu bound tasks running and no disk I/O
involved then full timeslices run out at ~114ms at 1000HZ (longer at lower
HZ) so that should be the longest period one task of the same priority could
possibly run before the others do. That sort of timeslice you would not pick
up at .1s interval 'top's but I find 'top' can be very deceiving if its
timing happens to be exactly what the intervals are it can look like only one
thing is running or one thing is stuck at the same priority and so on.
With actual numbers from interbench testing of fully cpu bound tasks (under
what's called benchmarking cpu of Gaming) the average and max scheduling
delays look of the same magnitude as mainline.
--
-ck
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
