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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E508EC433EF for ; Fri, 8 Oct 2021 11:11:09 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id CC53A61029 for ; Fri, 8 Oct 2021 11:11:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240126AbhJHLND (ORCPT ); Fri, 8 Oct 2021 07:13:03 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:26830 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239972AbhJHLNC (ORCPT ); Fri, 8 Oct 2021 07:13:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1633691466; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=beL+lHu4Yb6ST/YHe2oKhpNvDASDezmXv1HiQU4m3Qg=; b=SA248/MngBr4V+O4KWXJhqYVAUc4QN6L4IzeVRGNsOinXZY7NS/54RammEPuqkQj98XsgB s6ZNGsLjzAmIZkpjPmujpceUykyOnunkF0fMUSor4xJaGv8r0FEqnK7WRg3Am9LwtbT9V9 RmUVp+w3AHvi9PXJfmic+i2yr+iK6Io= Received: from mail-wr1-f69.google.com (mail-wr1-f69.google.com [209.85.221.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-205-pTNNBAx9OQWKbefmxyDfzg-1; Fri, 08 Oct 2021 07:11:05 -0400 X-MC-Unique: pTNNBAx9OQWKbefmxyDfzg-1 Received: by mail-wr1-f69.google.com with SMTP id h11-20020adfa4cb000000b00160c791a550so6857055wrb.6 for ; Fri, 08 Oct 2021 04:11:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=beL+lHu4Yb6ST/YHe2oKhpNvDASDezmXv1HiQU4m3Qg=; b=ZHpJ03DPrEHB5vcWU/6mCsOIm93eW+x7/I7Nge32E37az3dwsFYuC8/F+9aQVU7sRc 0yCD5a6+Lw/b5YQ0hkqFtuFyUetxIFc0CxtOr3td8lXFvjKtpkhSyHmvsjZyUV1PSQMP pE+kmR6ZpR6or8xQKqCACVtAgq6V+jBArov5VLxuvuSYRhDxt2H/jxEnmMlRB2ItTE40 J8o/ecpXe51o6y+lSAjsP3pmgLSydXYL5f7M66C+3+dlzGxKLQxS02yn2P+xGOKg/tlx cwIuTrAHfHK/5n+4BOIlGM6/3BbPFODgQn385u/tAJD/pKQo0BpVpUTHlzHNSvskuqlR RC3w== X-Gm-Message-State: AOAM5316jhU/WV5qOD7phkBcXBF3RSX8dCk2s0wDPSXhw8ESBp81Cg5k YegRcAOOCYWkUrnmCtfRD77G/1Efw8Pd/ND1mnifq+N4VBLvTa9WgBkBpOakX/FMf23WCopxIMV W/oGgz8wNwjzgIZQbS48uM8zX X-Received: by 2002:a7b:cb4b:: with SMTP id v11mr2775627wmj.155.1633691464372; Fri, 08 Oct 2021 04:11:04 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxJWz/YVYFIIpOplJfuo/FOI1MaHjPWY2n3Z2/U3ORFID7I1ioP6msn33W2JQQwEvNs6r+RHQ== X-Received: by 2002:a7b:cb4b:: with SMTP id v11mr2775600wmj.155.1633691464206; Fri, 08 Oct 2021 04:11:04 -0700 (PDT) Received: from vitty.brq.redhat.com (g-server-2.ign.cz. [91.219.240.2]) by smtp.gmail.com with ESMTPSA id z12sm780472wmk.38.2021.10.08.04.11.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 08 Oct 2021 04:11:03 -0700 (PDT) From: Vitaly Kuznetsov To: Greg Kroah-Hartman , Long Li Cc: Bart Van Assche , "longli@linuxonhyperv.com" , "linux-block@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-hyperv@vger.kernel.org" , Jonathan Corbet , KY Srinivasan , Haiyang Zhang , Stephen Hemminger , Wei Liu , Dexuan Cui , Bjorn Andersson , Hans de Goede , "Williams, Dan J" , Maximilian Luz , Mike Rapoport , Ben Widawsky , Jiri Slaby , Andra Paraschiv , Siddharth Gupta , Hannes Reinecke Subject: Re: [Patch v5 0/3] Introduce a driver to support host accelerated access to Microsoft Azure Blob for Azure VM In-Reply-To: References: Date: Fri, 08 Oct 2021 13:11:02 +0200 Message-ID: <87fstb3h6h.fsf@vitty.brq.redhat.com> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-hyperv@vger.kernel.org Greg Kroah-Hartman writes: ... > > Not to mention the whole crazy idea of "let's implement our REST api > that used to go over a network connection over an ioctl instead!" > That's the main problem that you need to push back on here. > > What is forcing you to put all of this into the kernel in the first > place? What's wrong with the userspace network connection/protocol that > you have today? > > Does this mean that we now have to implement all REST apis that people > dream up as ioctl interfaces over a hyperv transport? That would be > insane. As far as I understand, the purpose of the driver is to replace a "slow" network connection to API endpoint with a "fast" transport over Vmbus. So what if instead of implementing this new driver we just use Hyper-V Vsock and move API endpoint to the host? -- Vitaly