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 41846C433EF for ; Fri, 8 Oct 2021 13:29:32 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 215A760F90 for ; Fri, 8 Oct 2021 13:29:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242404AbhJHNb0 (ORCPT ); Fri, 8 Oct 2021 09:31:26 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:54921 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242369AbhJHNbW (ORCPT ); Fri, 8 Oct 2021 09:31:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1633699767; 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=W+20OtyOzoxeqzG//DN6kXf3yJzCYJkrDPENdiVWnik=; b=gVOfPl2CJ0uZglf3PUYDFwf3cju14SHcMOYpWUchvY+pMQuBQMYrpVaPctZtia+dyWmtT3 nnJKaA1kMkOC+Y0YYuYUrTPYfr6udpfZTGoV/Kv6h9d8XTsyw/LCZtA2Gy/5/tMDd1nscP LrLzQxKaK1AAno3lwvB+CUs7lCttXAA= 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-191-2p-B0ayQP1Wosehh6LitUA-1; Fri, 08 Oct 2021 09:29:02 -0400 X-MC-Unique: 2p-B0ayQP1Wosehh6LitUA-1 Received: by mail-wr1-f69.google.com with SMTP id l9-20020adfc789000000b00160111fd4e8so7359587wrg.17 for ; Fri, 08 Oct 2021 06:29:01 -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=W+20OtyOzoxeqzG//DN6kXf3yJzCYJkrDPENdiVWnik=; b=YwHTkejsOrTb/0YxbhEED7qlrboskyGi8BAEyhyiXeqpZFwN3N9LJQ/RCHT4rMz6AR 0Ulz/hA2MxKBAY215VcEvcW9foVtOchz0xXKtkWH6L96rx0ulR7UUW2WP7S5pk9NkToq 25TgRGWRG9zYm/zi+sK+KLJXSIitAuv69N5no6nhaFRnNAmBOk9HN/71HtBTW6WR1SDt XxNN07XqF46WZOHAQEMmkyrH0x07dKHkwlnD89aHwirxjrIempxXXZc3uBFfgrcH+fK+ JrbCpf0jaJkArwZBz8FQMK0Nmt9X2x9aytUslaHIzxlJhJ38oHlYE+b8v4bMH9YWInZD xeHw== X-Gm-Message-State: AOAM5316Nu5fa4gUjIBOW4ZsKKYDVDqCMiF2tWsSNmMKeZ+UFXMaI2wK JGkbTDHM6Xml3F1idY7vctBvzKtYRXNFw43K6NP/h+Kn4izv1fZn89UfR7gjAdDiojX01fyPj/K w58FufE1/h7uQeY9iJn1lISdR X-Received: by 2002:a7b:c341:: with SMTP id l1mr3467555wmj.142.1633699740959; Fri, 08 Oct 2021 06:29:00 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz3LlFeRzehp5jW/HXHcTYHvdvbDvy0R7E26tnAaFh6ZsgXTWn2Mhn+npR6fWXOMyfVrJ15AA== X-Received: by 2002:a7b:c341:: with SMTP id l1mr3467528wmj.142.1633699740777; Fri, 08 Oct 2021 06:29:00 -0700 (PDT) Received: from vitty.brq.redhat.com (g-server-2.ign.cz. [91.219.240.2]) by smtp.gmail.com with ESMTPSA id y4sm3451927wry.95.2021.10.08.06.28.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 08 Oct 2021 06:29:00 -0700 (PDT) From: Vitaly Kuznetsov To: Long Li Cc: Greg Kroah-Hartman , 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: <87fstb3h6h.fsf@vitty.brq.redhat.com> Date: Fri, 08 Oct 2021 15:28:58 +0200 Message-ID: <87a6jj3asl.fsf@vitty.brq.redhat.com> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Greg Kroah-Hartman writes: > On Fri, Oct 08, 2021 at 01:11:02PM +0200, Vitaly Kuznetsov wrote: >> 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. > > Given that the network connection is already over vmbus, how is this > "slow" today? I have yet to see any benchmark numbers anywhere :( > >> So what if instead of implementing this new driver we just use >> Hyper-V Vsock and move API endpoint to the host? > > What is running on the host in the hypervisor that is supposed to be > handling these requests? Isn't that really on some other guest? > Long, would it be possible to draw a simple picture for us describing the backend flow of the feature, both with network connection and with this new driver? We're struggling to understand which particular bottleneck the driver is trying to eliminate. -- Vitaly