Re: [PATCH RESEND v10 1/3] vhost: Add a new modparam to allow userspace select kthread

On Tue, Jun 3, 2025 at 3:34 PM Simon Horman wrote: > > On Sat, May 31, 2025 at 05:57:26PM +0800, Cindy Lu wrote: > > The vhost now uses vhost_task and workers as a child of the owner thread. > > While this aligns with containerization principles, it confuses some > > legacy userspace applications,

Re: [PATCH RESEND v10 1/3] vhost: Add a new modparam to allow userspace select kthread

On Sun, Jun 1, 2025 at 6:51 PM Michael S. Tsirkin wrote: > > On Sat, May 31, 2025 at 05:57:26PM +0800, Cindy Lu wrote: > > The vhost now uses vhost_task and workers as a child of the owner thread. > > While this aligns with containerization principles, it confuses some > > legacy userspace applica

Re: [PATCH RESEND v10 1/3] vhost: Add a new modparam to allow userspace select kthread

On Sat, May 31, 2025 at 05:57:26PM +0800, Cindy Lu wrote: > The vhost now uses vhost_task and workers as a child of the owner thread. > While this aligns with containerization principles, it confuses some > legacy userspace applications, therefore, we are reintroducing kthread > API support. > > A

Re: [PATCH RESEND v10 1/3] vhost: Add a new modparam to allow userspace select kthread

On Sat, May 31, 2025 at 05:57:26PM +0800, Cindy Lu wrote: > The vhost now uses vhost_task and workers as a child of the owner thread. > While this aligns with containerization principles, it confuses some > legacy userspace applications, therefore, we are reintroducing kthread > API support. > > A

[PATCH RESEND v10 1/3] vhost: Add a new modparam to allow userspace select kthread

The vhost now uses vhost_task and workers as a child of the owner thread. While this aligns with containerization principles, it confuses some legacy userspace applications, therefore, we are reintroducing kthread API support. Add a new module parameter to allow userspace to select behavior betwee