Shirley> I have done some patch like that on top of splitting
Shirley> CQ. The problem I found that hardware interrupt favors
Shirley> one CPU. Most of the time these two threads are running
Shirley> on the same cpu according to my debug output. You can
Shirley> easily find out by cat /proc/interrupts and
Shirley> /proc/irq/XXX/smp_affinity. ehca has distributed
Shirley> interrupts evenly on SMP, so it gets the benefits of two
Shirley> threads, and gains much better throughputs.
Yes, an interrupt will likely be delivered to one CPU.
But there's no reason why the two threads can't be pinned to different
CPUs or given exclusive CPU masks, exactly the same way that ehca
implements it.
- R.
-
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]
