From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0C25EEB64D8 for ; Wed, 14 Jun 2023 06:03:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242516AbjFNGDm (ORCPT ); Wed, 14 Jun 2023 02:03:42 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:32978 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233669AbjFNGDj (ORCPT ); Wed, 14 Jun 2023 02:03:39 -0400 Received: from out01.mta.xmission.com (out01.mta.xmission.com [166.70.13.231]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 94F1D1AA for ; Tue, 13 Jun 2023 23:03:37 -0700 (PDT) Received: from in02.mta.xmission.com ([166.70.13.52]:36596) by out01.mta.xmission.com with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1q9JbT-009Rpp-9K; Wed, 14 Jun 2023 00:03:35 -0600 Received: from ip68-110-29-46.om.om.cox.net ([68.110.29.46]:55536 helo=email.froward.int.ebiederm.org.xmission.com) by in02.mta.xmission.com with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1q9JbJ-003KA2-K3; Wed, 14 Jun 2023 00:03:34 -0600 From: "Eric W. Biederman" To: Mike Christie Cc: Oleg Nesterov , linux@leemhuis.info, nicolas.dichtel@6wind.com, axboe@kernel.dk, torvalds@linux-foundation.org, linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org, mst@redhat.com, sgarzare@redhat.com, jasowang@redhat.com, stefanha@redhat.com, brauner@kernel.org References: <20230601183232.8384-1-michael.christie@oracle.com> <20230602192254.GD555@redhat.com> <87r0qt18qq.fsf_-_@email.froward.int.ebiederm.org> <20230605151037.GE32275@redhat.com> <03c07f48-8922-f563-560c-f0d4cc3e1279@oracle.com> <20230606121643.GD7542@redhat.com> <39f5913c-e658-e476-0378-62236bb4ed49@oracle.com> <20230606193907.GB18866@redhat.com> Date: Wed, 14 Jun 2023 01:02:58 -0500 In-Reply-To: (Mike Christie's message of "Tue, 6 Jun 2023 15:38:04 -0500") Message-ID: <87mt12oa25.fsf_-_@email.froward.int.ebiederm.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-XM-SPF: eid=1q9JbJ-003KA2-K3;;;mid=<87mt12oa25.fsf_-_@email.froward.int.ebiederm.org>;;;hst=in02.mta.xmission.com;;;ip=68.110.29.46;;;frm=ebiederm@xmission.com;;;spf=pass X-XM-AID: U2FsdGVkX1/4Ah0HgiSeh15/g7eNi4deF/0irVfxcS8= X-SA-Exim-Connect-IP: 68.110.29.46 X-SA-Exim-Mail-From: ebiederm@xmission.com Subject: Can vhost translate to io_uring? X-SA-Exim-Version: 4.2.1 (built Sat, 08 Feb 2020 21:53:50 +0000) X-SA-Exim-Scanned: Yes (on in02.mta.xmission.com) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I am sad my idea for simplifying things did not work out. Let's try an even bigger idea to reduce maintenance and simplify things. Could vhost depend on io_uring? Could vhost just be a translation layer of existing vhost requests to io_uring requests? At a quick glance it looks like io_uring already supports the functionality that vhost supports (which I think is networking and scsi). If vhost could become a translation layer that would allow removing the vhost worker and PF_USER_WORKER could be removed completely, leaving only PF_IO_WORKER. I suggest this because a significant vhost change is needed because in the long term the hacks in exec and coredump are not a good idea. Which means something like my failed "[PATCH v3] fork, vhost: Use CLONE_THREAD to fix freezer/ps regression". If we have to go to all of the trouble of reworking things it why can't we just make io_uring do all of the work? Eric