On Mon, Nov 5, 2018 at 9:49 PM Jason Wang <jasowang@xxxxxxxxxx> wrote: > If you allow device to specify the worker itself, you can do any kinds > of mapping bettween work and worker kthread I think. The advantage of > doing this is that you can keep the vhost-net untouched. This makes > things a little bit easier and proving two kthreads is better than one > for -net workload is probably not as easy as it looks. We may get boost > in some cases but degradation for the rest. Sounds good. 1 worker is created by vhost as today, all the others are entering from userspace via ioctl. -- wbr, Vitaly
