Hacker News new | past | comments | ask | show | jobs | submit login

Yes, if you don't want all interrupts to handled by CPU0 you'll need a different approach. But doing anything else may be more difficult than it sounds. Do you know if the bug mentioned here is fixed?


http://code.google.com/p/irqbalance is 403 for me and I haven't been able to check.

Setting IRQ affinity for network controllers to either follow or not follow the "high priority" processes seems to do the trick.

I usually do stuff described here:


And sometimes following ends up better (same cache), sometimes isolating ends up being better.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact