[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACGkMEsrpAXz-opeJMkPC7h-3H3POGppZk7_Ke+mO3nyG5y7iQ@mail.gmail.com>
Date: Thu, 12 Sep 2024 09:47:24 +0800
From: Jason Wang <jasowang@...hat.com>
To: "Michael S. Tsirkin" <mst@...hat.com>
Cc: Mike Christie <michael.christie@...cle.com>, Cindy Lu <lulu@...hat.com>,
linux-kernel@...r.kernel.org, virtualization@...ts.linux-foundation.org
Subject: Re: [RESEND PATCH v1 0/7]vhost: Add support of kthread API
On Thu, Sep 12, 2024 at 3:02 AM Michael S. Tsirkin <mst@...hat.com> wrote:
>
> On Wed, Sep 11, 2024 at 11:20:30AM -0500, Mike Christie wrote:
> > If people are ok with something similar as in this patchset where
> > we have both vhost_tasks and kthreads, then I can send something.
>
>
> It would be better, as you say, to modify the vhost_task code so it can
> emulate the kthread behavior. However, given that apparently some users
> are unhappy, what you describe would be a good stopgap solution
> until we have that.
>
> The main difficulty seems to be to describe what the
> behaviour is, exactly, so userspace can make informed
> decisions on what to use.
Exactly.
Thanks
>
> --
> MST
>
Powered by blists - more mailing lists