Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20181102160710.3741-1-v.mayatskih@gmail.com> <20181102160710.3741-2-v.mayatskih@gmail.com>
 <fe79c7fd-1e9f-dab8-3c65-8151181c922c@redhat.com> <CAGF4SLgDk+48aLKHhA_ZgRc6D30tGdnB89b5m5bZKwzyoDb0dQ@mail.gmail.com>
 <617e0c54-7d11-09b6-21e5-968260107872@redhat.com>
In-Reply-To: <617e0c54-7d11-09b6-21e5-968260107872@redhat.com>
From:   Vitaly Mayatskih <v.mayatskih@gmail.com>
Date:   Mon, 5 Nov 2018 21:59:31 -0500
Message-ID: <CAGF4SLhXq0x+eJcVzE6G_PoDv93bXnu1h=D24NRLXVsoMeEHJg@mail.gmail.com>
Subject: Re: [PATCH 1/1] vhost: add per-vq worker thread
To:     Jason Wang <jasowang@redhat.com>
Cc:     "Michael S . Tsirkin" <mst@redhat.com>, kvm@vger.kernel.org,
        virtualization@lists.linux-foundation.org, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Mon, Nov 5, 2018 at 9:49 PM Jason Wang <jasowang@redhat.com> 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