From: Christoph Hellwig <hch@infradead.org>
To: Mike Christie <michael.christie@oracle.com>
Cc: hch@infradead.org, stefanha@redhat.com, jasowang@redhat.com,
mst@redhat.com, sgarzare@redhat.com,
virtualization@lists.linux-foundation.org, brauner@kernel.org,
ebiederm@xmission.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v10 0/8] Use copy_process in vhost layer
Date: Mon, 11 Jul 2022 21:54:45 -0700 [thread overview]
Message-ID: <Ysz+lXEkjlBXBC65@infradead.org> (raw)
In-Reply-To: <319f1e21-6cf4-4502-ebc8-c808560fb48d@oracle.com>
On Mon, Jul 11, 2022 at 11:44:14PM -0500, Mike Christie wrote:
> Eric and Christian, Ping?
>
> If you guys don't like these patches anymore what about something
> simple like just exporting some helpers to update and check a task's
> nproc limit. Something like this:
I'm not Eric or Christian and don't really feel qualified on the
technical aspects here, but please drop the pointless externs while
you're at it :)
next prev parent reply other threads:[~2022-07-12 4:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 1:13 Mike Christie
2022-06-20 1:13 ` [PATCH v10 1/8] fork: Make IO worker options flag based Mike Christie
2022-06-20 1:13 ` [PATCH v10 2/8] fork/vm: Move common PF_IO_WORKER behavior to new flag Mike Christie
2022-06-20 1:13 ` [PATCH v10 3/8] fork: add USER_WORKER flag to not dup/clone files Mike Christie
2022-06-20 1:13 ` [PATCH v10 4/8] fork: Add USER_WORKER flag to ignore signals Mike Christie
2022-06-20 1:13 ` [PATCH v10 5/8] fork: allow kernel code to call copy_process Mike Christie
2022-06-20 1:13 ` [PATCH v10 6/8] vhost_task: Allow vhost layer to use copy_process Mike Christie
2022-06-20 1:13 ` [PATCH v10 7/8] vhost: move worker thread fields to new struct Mike Christie
2022-06-20 1:13 ` [PATCH v10 8/8] vhost: use vhost_tasks for worker threads Mike Christie
2022-07-12 4:44 ` [PATCH v10 0/8] Use copy_process in vhost layer Mike Christie
2022-07-12 4:54 ` Christoph Hellwig [this message]
2022-07-14 13:02 ` Christian Brauner
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=Ysz+lXEkjlBXBC65@infradead.org \
--to=hch@infradead.org \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.christie@oracle.com \
--cc=mst@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@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
all inboxes | Powered by JetHome®