On Sat, 24 Jul 2010, Alexander Motin wrote:
Doug Barton wrote:
On Sat, 24 Jul 2010, Alexander Motin wrote:
Author: mav
Date: Sat Jul 24 10:49:59 2010
New Revision: 210444
URL: http://svn.freebsd.org/changeset/base/210444
Log:
Increment td->td_intr_nesting_level for LAPIC timer interrupts. Among
other
things it hints SCHED_ULE to run clock swi handlers on their native
CPUs,
avoiding many unneeded IPI_PREEMPT calls.
Will this help SCHED_4BSD at all? I'm finding it to be slightly better
for interactivity on a loaded system, but frankly at this point they
both leave a lot to be desired.
At least not directly. SCHED_4BSD doesn't use this variable. But I have
no idea if the problem exist there. Even on SCHED_ULE it happens only in
some cases, if swi thread was accidentally pushed out of it's CPU by
higher priority thread. 4BSD has different migration logic, so behavior
could be different there.
Ok, thanks.
Doug
--
Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/
Computers are useless. They can only give you answers.
-- Pablo Picasso
_______________________________________________
svn-src-head@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-head
To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org"
