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 ws5-mx01.kavi.com (ws5-mx01.kavi.com [34.193.7.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 8C46CC7619A for ; Wed, 12 Apr 2023 05:27:43 +0000 (UTC) Received: from lists.oasis-open.org (oasis.ws5.connectedcommunity.org [10.110.1.242]) by ws5-mx01.kavi.com (Postfix) with ESMTP id 06CFC370E0 for ; Wed, 12 Apr 2023 05:27:43 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id D6F249865B3 for ; Wed, 12 Apr 2023 05:27:42 +0000 (UTC) Received: from host09.ws5.connectedcommunity.org (host09.ws5.connectedcommunity.org [10.110.1.97]) by lists.oasis-open.org (Postfix) with QMQP id C1CB4986509; Wed, 12 Apr 2023 05:27:42 +0000 (UTC) Mailing-List: contact virtio-dev-help@lists.oasis-open.org; run by ezmlm List-ID: Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id ADDFC98650F for ; Wed, 12 Apr 2023 05:27:42 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: a0IwVX14ML-V_LdT_9UwHw-1 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681277259; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=UKUYr0lNtaArgZLaZ7jsbZFBZusg6bzDKx0cr/KAQEw=; b=ymKwZqkeuUrln+qfzD1dgjsPZWzFxAP6yBG5tH3KRhUHIzfmywRp/uYvUKfMVwLh7U cq9HNxwxySoHpYGdm5ShxQ7CwFxAyFYWSumwKu4olLdPxyME4d/NadMVCM6TIBSHaqGX h5KNYTTtVv27t6eJ849sGYcxb3qzetGexEZ/s2s7ESfIQKk5LevTklu4CNTlj5wtOb2v 5dJPaz47DM/tpDGjw40BJfeW2KUR4mK9gpjGppx5DiVOk6HFxan2X7R8UZSi+dYbuizN FttCWhXMsuEgFN9FkZNnMPJGF7PpAvO5X+Lbai9jtlR/OgQoYt8eOIrvqON1j6wjfsSb zZNw== X-Gm-Message-State: AAQBX9eMKYssm9GyYR1NDNDMDVQKr5v/0whxFbhh7yQLc3820AsLLJOQ gv9wTQ+TP65VfPlB9g7twwJHwWP+qvXC8S8MR2qzIqvW1r2nXePvyFORp9yGCBqixAmqaWWfb+Z TCaCWQ8K0HZtkynZzOvPiuHPe6eGv X-Received: by 2002:a05:600c:2307:b0:3ed:2709:2edf with SMTP id 7-20020a05600c230700b003ed27092edfmr12585963wmo.13.1681277259799; Tue, 11 Apr 2023 22:27:39 -0700 (PDT) X-Google-Smtp-Source: AKy350Y2EEceFQsuYBKrKq8mUU+RYE+mpxz/4dns/XfRt7k7TOhorlaLTZ8PU38z7C6AGSENcuPGzQ== X-Received: by 2002:a05:600c:2307:b0:3ed:2709:2edf with SMTP id 7-20020a05600c230700b003ed27092edfmr12585958wmo.13.1681277259512; Tue, 11 Apr 2023 22:27:39 -0700 (PDT) Date: Wed, 12 Apr 2023 01:27:35 -0400 From: "Michael S. Tsirkin" To: Parav Pandit Cc: "virtio-dev@lists.oasis-open.org" , "cohuck@redhat.com" , "virtio-comment@lists.oasis-open.org" , Shahaf Shuler , Satananda Burla Message-ID: <20230412012547-mutt-send-email-mst@kernel.org> References: <20230330225834.506969-1-parav@nvidia.com> <20230330225834.506969-11-parav@nvidia.com> <20230412003006-mutt-send-email-mst@kernel.org> <20230412004152-mutt-send-email-mst@kernel.org> <20230412010224-mutt-send-email-mst@kernel.org> <20230412011222-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [virtio-dev] Re: [virtio-comment] Re: [PATCH 10/11] transport-pci: Use driver notification PCI capability On Wed, Apr 12, 2023 at 05:24:57AM +0000, Parav Pandit wrote: > > > > From: virtio-comment@lists.oasis-open.org > open.org> On Behalf Of Michael S. Tsirkin > > > > Such registers do not start the VQ data path engines. > > > 1.x spec has done the right thing to have dedicated notification region which > > something an actual pci hw can implement. > > > > okay so.. in fact it turns out existing hardware is not really happy to emulate > > legacy. it does not really fit that well. > > so maybe we should stop propagating the legacy interface to modern hardware > > then. > It is not about current hw, utilize what hw has to offer and utilize what sw has to offer. > The key efficiency is coming by reusing what 1.x has already to offer. Just ... no. Either run 0.X or 1.X. This mix opens a ton of corner cases. NOTIFICATION_DATA is just off the top of my head, there's more for sure. It's a can of worms we won't be able to close. > > Add the legacy net header size feature and be done with it. > Hypervisor need to mediate and participate in all life cycle of the device. > > One wants to run the block device too. Current proposal with other changes we discussed cover wider case. --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org