From: "Michael S. Tsirkin" <mst@redhat.com>
To: Mike Christie <michael.christie@oracle.com>
Cc: Cindy Lu <lulu@redhat.com>,
jasowang@redhat.com, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [RESEND PATCH v1 0/7]vhost: Add support of kthread API
Date: Wed, 11 Sep 2024 15:02:04 -0400 [thread overview]
Message-ID: <20240911150013-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <85fb3a90-fbf4-4925-8b53-197f3faa574d@oracle.com>
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.
--
MST
next prev parent reply other threads:[~2024-09-11 19:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 2:00 [RESEND PATCH v1 0/7]vhost: Add support of kthread API Cindy Lu
2024-09-09 2:00 ` [RESEND PATCH v1 1/7] vhost: Add a new module_param for enable kthread Cindy Lu
2024-09-10 5:12 ` kernel test robot
2024-09-09 2:00 ` [RESEND PATCH v1 2/7] vhost: Add kthread support in function vhost_worker_queue() Cindy Lu
2024-09-09 2:00 ` [RESEND PATCH v1 3/7] vhost: Add kthread support in function vhost_workers_free() Cindy Lu
2024-09-09 2:00 ` [RESEND PATCH v1 4/7] vhost: Add the vhost_worker to support kthread Cindy Lu
2024-09-09 2:00 ` [RESEND PATCH v1 5/7] vhost: Add the cgroup related function Cindy Lu
2024-09-09 2:00 ` [RESEND PATCH v1 6/7] vhost: Add kthread support in function vhost_worker_create Cindy Lu
2024-09-09 2:00 ` [RESEND PATCH v1 7/7] vhost: Add new UAPI to support change to task mode Cindy Lu
2024-09-10 7:41 ` [RESEND PATCH v1 0/7]vhost: Add support of kthread API Michael S. Tsirkin
2024-09-10 8:37 ` Jason Wang
2024-09-10 8:42 ` Michael S. Tsirkin
2024-09-11 3:45 ` Jason Wang
2024-09-11 10:28 ` Michael S. Tsirkin
2024-09-11 16:17 ` Mike Christie
[not found] ` <CACGkMEvAR_2j=PdKZZyAZ1yK7H5OO+Ldc0Eygwyo8rMR=_uGBQ@mail.gmail.com>
2024-09-23 1:15 ` Cindy Lu
2024-09-11 16:20 ` Mike Christie
2024-09-11 19:02 ` Michael S. Tsirkin [this message]
2024-09-12 1:47 ` Jason Wang
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=20240911150013-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=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;
as well as URLs for NNTP newsgroup(s).