xen-netback in linux 3.12

xen-netback in linux 3.12

[xu cong]

[-- Attachment #1.1: Type: text/plain, Size: 503 bytes --]

Hi all,

I found xen-netback changed a lot in latest kernel. The shared xen-netback
threads in driver domain is replaced by per-vif kernel thread. In my
platform, I found the I/O throughput and scalability of per-vif netback is
better than previous implementation. Another advantage is that I can use
cgroups to control the CPU fair share among all VMs in driver domain (I
group netback thread and blkback thread for each VM). Is there any other
motivation for this modification? Thanks.

Regards,
Cong

[-- Attachment #1.2: Type: text/html, Size: 568 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: xen-netback in linux 3.12

[Zoltan Kiss]

On 17/01/14 21:30, xu cong wrote:
> Hi all,
>
> I found xen-netback changed a lot in latest kernel. The shared
> xen-netback threads in driver domain is replaced by per-vif kernel
> thread. In my platform, I found the I/O throughput and scalability of
> per-vif netback is better than previous implementation. Another
> advantage is that I can use cgroups to control the CPU fair share among
> all VMs in driver domain (I group netback thread and blkback thread for
> each VM). Is there any other motivation for this modification? Thanks.

as far as I remember scalability was the only motivation. Previously you 
could end in a situation where one thread (pinned to a vCPU) did a lot 
of work while others nothing. In this thread-per-VIF model the kernel 
has the ability to schedule the workloads as it want, and users can also 
poke around with settings.

Zoli