Yunsong (Roamer) Lu wrote:
I've not made progress on this. I was looking at changing intrd, to
improve its allocation of processor interrupts, but I got stymied when
the processor folks couldn't seem to agree on any set of rules for how
interrupt allocation should be done. (Same core, different core?
Results seem to vary based on the particular CPU and the nature of the
workload. Makes it hard to code up a set of rules when we don't even
know what the rules should be.)
If making i_ddi_intr_get_cpuid() work is a blocking factor for progress,
then I can work on that. I didn't understand that this particular part
of the problem was needing a solution.
-- Garrett
> Garret,
> Could you give an update if any progress? I didn't look into it.
>
> Roamer
>
> Sunay Tripathi wrote:
>
>> Garrett/Roamer,
>>
>> Have you made any progress with interrupt retargetting code. Basically,
>> when a cpu list is specified via '-C' option for a NIC/VNIC or flow,
>> we need to do two things:
>> 1) Make i_ddi_intr_get_cpuid() work so in case of NIC having a single
>> interrupt, we can assign it to one of the specified CPUs if the
>> CPU list is specified for a NIC.
>> 2) In case the NIC supports MSI-X interrupt, we should be able to assign
>> the interrupt for the Rx ring to one of the specified CPUs.
>>
>> Which also means that the MAC to driver APIs need to be strong enough to
>> be able to associate a MSI-X interrupt with a Rx ring (Kais??).
>>
>> Cheers,
>> Sunay
>>
>>
>
>
