On Wed, Apr 05, 2017 at 07:06:18PM -0000, I AM USER wrote:
Thanks a lot for a pedagogical reply. You are correct on (b). I am not using CPU pinning,
that's a requirement I can't change. For (a), I didn't understand your point
about 'sriov' ? What is that ? I am using virtio driver for the bridged ethernet.
I figured, I just wanted to ask. SRIOV is a technology that allows you as host
administrator to "pass through" a pci function directly to a guess, so as to
accelerate network traffic from said guest to the wire. It creates a situation
in which irqs can be handled directly by the guest, and is cause to potentially
run irqbalance in the guest.
Since you are using virtio though, you really don't need irqbalance there
I see what you are saying about irqbalance. Can I ask, if there are
any formal recommendation on CPU pinning for Fedora or red hat derivatives ?
That would be a question for people working on the virt bits. I think the best
answer I can give is "it depends on your workload"
In a follow up question, what kernel config options are desirable for
non-CPU pinning ?
None that can be asserted universally with the information given.
> kernel mailing list -- kernel(a)lists.fedoraproject.org
> To unsubscribe send an email to kernel-leave(a)lists.fedoraproject.org