On Tue, 2007-11-20 at 16:50 -0500, Mathieu Desnoyers wrote:
> Then my original point is valid : put_no_resched() will cause unwanted
> scheduler latencies. It's designed only to be used from within the
> scheduler code itself. The correct approach would be a standard
> put_cpu().
>
> Or am I missing something ?
Then someone who cares about scheduler latency had better audit the code
and figure out which calls are made under spinlock, and which aren't:
it's not on my personal list of high priorities. I'll be happy to review
any patches, though.
Trond
-
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]
