Eric W. Biederman wrote:
There is still a question of how to handle the NUMA case but...
the numa case is already handled; the needed info for that is exposed already enough... at least for irqbalance
- 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/
- Follow-Ups:
- References:
- [patch] Add allowed_affinity to the irq_desc to make it possible to have restricted irqs
- From: Arjan van de Ven <[email protected]>
- Re: [patch] Add allowed_affinity to the irq_desc to make it possible to have restricted irqs
- From: [email protected] (Eric W. Biederman)
- Re: [patch] Add allowed_affinity to the irq_desc to make it possible to have restricted irqs
- From: Ingo Molnar <[email protected]>
- Re: [patch] Add allowed_affinity to the irq_desc to make it possible to have restricted irqs
- From: [email protected] (Eric W. Biederman)
- [patch] Add allowed_affinity to the irq_desc to make it possible to have restricted irqs
- Prev by Date: Re: [patch] Add allowed_affinity to the irq_desc to make it possible to have restricted irqs
- Next by Date: Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!
- Previous by thread: Re: [patch] Add allowed_affinity to the irq_desc to make it possible to have restricted irqs
- Next by thread: Re: [patch] Add allowed_affinity to the irq_desc to make it possible to have restricted irqs
- Index(es):
 |