| From: |
| Mike Christie <michael.christie-AT-oracle.com> |
| To: |
| oleg-AT-redhat.com, linux-AT-leemhuis.info, nicolas.dichtel-AT-6wind.com, axboe-AT-kernel.dk, ebiederm-AT-xmission.com, torvalds-AT-linux-foundation.org, linux-kernel-AT-vger.kernel.org, virtualization-AT-lists.linux-foundation.org, mst-AT-redhat.com, sgarzare-AT-redhat.com, jasowang-AT-redhat.com, stefanha-AT-redhat.com, brauner-AT-kernel.org |
| Subject: |
| [RFC PATCH 0/8] vhost_tasks: Use CLONE_THREAD/SIGHAND |
| Date: |
| Wed, 17 May 2023 19:09:12 -0500 |
| Message-ID: |
| <20230518000920.191583-1-michael.christie@oracle.com> |
| Archive-link: |
| Article |
This patch allows the vhost and vhost_task code to use CLONE_THREAD,
CLONE_SIGHAND and CLONE_FILES. It's a RFC because I didn't do all the
normal testing, haven't coverted vsock and vdpa, and I know you guys
will not like the first patch. However, I think it better shows what
we need from the signal code and how we can support signals in the
vhost_task layer.
Note that I took the super simple route and kicked off some work to
the system workqueue. We can do more invassive approaches:
1. Modify the vhost drivers so they can check for IO completions using
a non-blocking interface. We then don't need to run from the system
workqueue and can run from the vhost_task.
2. We could drop patch 1 and just say we are doing a polling type
of approach. We then modify the vhost layer similar to #1 where we
can check for completions using a non-blocking interface and use
the vhost_task task.
