virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jason Wang <jasowang@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>, Cindy Lu <lulu@redhat.com>,
	mst@redhat.com, linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org
Subject: Re: [RFC 7/7] vhost: Add new UAPI to support changing Kthread mode
Date: Sun, 25 Aug 2024 23:26:37 -0700	[thread overview]
Message-ID: <ZswgHTRUR-wstAHf@infradead.org> (raw)
In-Reply-To: <CACGkMEv=cQqXeLdsM1ivOFvUcG+-eOOwHE_BVQmF_scbqYxUpg@mail.gmail.com>

On Mon, Aug 26, 2024 at 02:21:52PM +0800, Jason Wang wrote:
> > What is the application visible behavior that the API use is the proxy
> > for?
> 
> Vhost used to be created by kthreadd but some recent patches change it
> to behave like being froked by the owner. So the various attributes
> that interhit from the parent has been changed (scheduling and
> namespace etc).

Well, if that breaks userspace it needs to be changed to opt into the
new behavior rather than requiring a flag to not break the existing
applications.  Assuming the change is intentional to start with.


  reply	other threads:[~2024-08-26  6:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-19  9:27 [RFC 0/7] vhost: Add support of kthread API Cindy Lu
2024-08-19  9:27 ` [RFC 1/7] vhost: Add a new module_param for enable kthread Cindy Lu
2024-08-19  9:27 ` [RFC 2/7] vhost: Add kthread support in function vhost_worker_queue() Cindy Lu
2024-08-27  2:36   ` Jason Wang
2024-08-28  9:32     ` Cindy Lu
2024-08-19  9:27 ` [RFC 3/7] vhost: Add kthread support in function vhost_workers_free() Cindy Lu
2024-08-19  9:27 ` [RFC 4/7] vhost: Add the vhost_worker to support kthread Cindy Lu
2024-08-19  9:27 ` [RFC 5/7] vhost: Add the cgroup related function Cindy Lu
2024-08-19  9:27 ` [RFC 6/7] vhost: Add kthread support in function vhost_worker_create Cindy Lu
2024-08-19  9:27 ` [RFC 7/7] vhost: Add new UAPI to support changing Kthread mode Cindy Lu
2024-08-21  5:06   ` Christoph Hellwig
2024-08-25 13:51     ` Cindy Lu
2024-08-26  6:21     ` Jason Wang
2024-08-26  6:26       ` Christoph Hellwig [this message]
2024-08-27  2:09         ` Jason Wang
2024-08-27  2:30           ` Jason Wang
2024-08-27  2:32   ` Jason Wang
2024-08-28  9:46     ` Cindy Lu
2024-08-27  2:36   ` Jason Wang
2024-08-27  2:35 ` [RFC 0/7] vhost: Add support of kthread API Jason Wang
2024-08-28  9:47   ` Cindy Lu

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=ZswgHTRUR-wstAHf@infradead.org \
    --to=hch@infradead.org \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lulu@redhat.com \
    --cc=mst@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;
as well as URLs for NNTP newsgroup(s).