From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cindy Lu <lulu@redhat.com>
Cc: jasowang@redhat.com, michael.christie@oracle.com,
sgarzare@redhat.com, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org
Subject: Re: [PATCH RESEND v10 1/3] vhost: Add a new modparam to allow userspace select kthread
Date: Sun, 1 Jun 2025 06:51:32 -0400 [thread overview]
Message-ID: <20250601064917-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20250531095800.160043-2-lulu@redhat.com>
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.
>
> Add a new module parameter to allow userspace to select behavior
> between using kthread and task.
>
> By default, this parameter is set to true (task mode). This means the
> default behavior remains unchanged by this patch.
>
> Signed-off-by: Cindy Lu <lulu@redhat.com>
So modparam is here but does nothing.
This should be the last patch in the series, or squashed with 3/3.
why is this inherit_owner but ioctl is fork_owner? is there
a difference? If not
can't the name be consistent with the ioctl? vhost_fork_owner?
> ---
> drivers/vhost/vhost.c | 5 +++++
> drivers/vhost/vhost.h | 10 ++++++++++
> 2 files changed, 15 insertions(+)
>
> diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c
> index 3a5ebb973dba..240ba78b1e3f 100644
> --- a/drivers/vhost/vhost.c
> +++ b/drivers/vhost/vhost.c
> @@ -41,6 +41,10 @@ static int max_iotlb_entries = 2048;
> module_param(max_iotlb_entries, int, 0444);
> MODULE_PARM_DESC(max_iotlb_entries,
> "Maximum number of iotlb entries. (default: 2048)");
> +bool inherit_owner_default = true;
> +module_param(inherit_owner_default, bool, 0444);
> +MODULE_PARM_DESC(inherit_owner_default,
> + "Set task mode as the default(default: Y)");
>
> enum {
> VHOST_MEMORY_F_LOG = 0x1,
> @@ -552,6 +556,7 @@ void vhost_dev_init(struct vhost_dev *dev,
> dev->byte_weight = byte_weight;
> dev->use_worker = use_worker;
> dev->msg_handler = msg_handler;
> + dev->inherit_owner = inherit_owner_default;
> init_waitqueue_head(&dev->wait);
> INIT_LIST_HEAD(&dev->read_list);
> INIT_LIST_HEAD(&dev->pending_list);
> diff --git a/drivers/vhost/vhost.h b/drivers/vhost/vhost.h
> index bb75a292d50c..c1ff4a92b925 100644
> --- a/drivers/vhost/vhost.h
> +++ b/drivers/vhost/vhost.h
> @@ -176,6 +176,16 @@ struct vhost_dev {
> int byte_weight;
> struct xarray worker_xa;
> bool use_worker;
> + /*
> + * If inherit_owner is true we use vhost_tasks to create
> + * the worker so all settings/limits like cgroups, NPROC,
> + * scheduler, etc are inherited from the owner. If false,
> + * we use kthreads and only attach to the same cgroups
> + * as the owner for compat with older kernels.
> + * here we use true as default value.
> + * The default value is set by modparam inherit_owner_default
> + */
> + bool inherit_owner;
> int (*msg_handler)(struct vhost_dev *dev, u32 asid,
> struct vhost_iotlb_msg *msg);
> };
> --
> 2.45.0
next prev parent reply other threads:[~2025-06-01 10:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-31 9:57 [PATCH RESEND v10 0/3] vhost: Add support of kthread API Cindy Lu
2025-05-31 9:57 ` [PATCH RESEND v10 1/3] vhost: Add a new modparam to allow userspace select kthread Cindy Lu
2025-06-01 10:51 ` Michael S. Tsirkin [this message]
2025-06-05 7:34 ` Cindy Lu
2025-06-03 7:34 ` Simon Horman
2025-06-05 7:35 ` Cindy Lu
2025-05-31 9:57 ` [PATCH RESEND v10 2/3] vhost: Reintroduce kthread mode support in vhost Cindy Lu
2025-05-31 9:57 ` [PATCH RESEND v10 3/3] vhost: Add new UAPI to select kthread mode and KConfig to enable this IOCTL Cindy Lu
2025-06-01 10:49 ` Michael S. Tsirkin
2025-06-05 7:34 ` Cindy Lu
2025-06-04 6:00 ` [PATCH RESEND v10 0/3] vhost: Add support of kthread API Lei Yang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250601064917-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=michael.christie@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=sgarzare@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox