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 93E8EC47074 for ; Wed, 15 Nov 2023 07:52:01 +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 AFE0A72349 for ; Wed, 15 Nov 2023 07:52:00 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 99CD9986DA0 for ; Wed, 15 Nov 2023 07:52:00 +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 80199986D99; Wed, 15 Nov 2023 07:52:00 +0000 (UTC) Mailing-List: contact virtio-comment-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 6CD32986D9A for ; Wed, 15 Nov 2023 07:52:00 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: KrZBYKcVPUCEofMHBxVNXA-1 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700034717; x=1700639517; 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=4NPEvH4lO5C1rsexMQFUBIDfNQNLBpnivAn85zHjx+Q=; b=hAUMylI6R98bHvjW/fum2rrga07l5IGxLETvsmtjD1RRo/CQ/Mcz1RTPSQu+0VhHpg vZEV/IQGoBDpmlEdu14uB95AoYUKDkrFfFK95OHauThnZNflkFWE+waboo9+zFhb8mDC aX1aQ5MsHEtvHuT4boz6U/yDrg5RB6uT62+KvnaIuMQlVYXh3banlsdkLne3GSHVEoB/ pmtE2U0pPMURsmcgj6VdHgP+dMxvNjkZF02k/oaJRP7oqfVl/e25CzIezhGOC9yC/WJ8 +CV2TbDHgWKt6RcBq7FdYsL7VIV2bozUNZWeTnNQTl4PJpeb1ViBwSFdb7MqR1+EJH5I xJnw== X-Gm-Message-State: AOJu0Yy5yItWISca+XLgg+Xi48mlV9tR/bLfnkv5OiZstF953RKLROwv vjRwXjFgalReuddpDTr+6oLjex7HyK35SgjuPx/IYx0DzyGNpOILMKfk15auykWCDPh/qVAsx0E kCUcFBXGXYVyO0FiHkiLi77JBW51813084Q== X-Received: by 2002:a17:906:ecea:b0:9bf:6200:fe33 with SMTP id qt10-20020a170906ecea00b009bf6200fe33mr8759003ejb.16.1700034716912; Tue, 14 Nov 2023 23:51:56 -0800 (PST) X-Google-Smtp-Source: AGHT+IEAJWJR12vtt/bA9ZV6tZiwJlpofVXGefJodT8MPvkDQ2FxbPszHZBs0zC1sReap5CwGpEEog== X-Received: by 2002:a17:906:ecea:b0:9bf:6200:fe33 with SMTP id qt10-20020a170906ecea00b009bf6200fe33mr8758984ejb.16.1700034716592; Tue, 14 Nov 2023 23:51:56 -0800 (PST) Date: Wed, 15 Nov 2023 02:51:52 -0500 From: "Michael S. Tsirkin" To: "Zhu, Lingshan" Cc: Jason Wang , Parav Pandit , "virtio-comment@lists.oasis-open.org" , "cohuck@redhat.com" , "sburla@marvell.com" , Shahaf Shuler , Maor Gottlieb , Yishai Hadas Message-ID: <20231115025002-mutt-send-email-mst@kernel.org> References: <20231107015412-mutt-send-email-mst@kernel.org> <20231108025854-mutt-send-email-mst@kernel.org> <20231109022647-mutt-send-email-mst@kernel.org> <20231113013016-mutt-send-email-mst@kernel.org> <9952859f-1b72-46bf-b386-7c3f5c69269f@intel.com> <20231114032553-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-comment] Re: [PATCH v3 6/8] admin: Add theory of operation for write recording commands On Wed, Nov 15, 2023 at 12:05:59PM +0800, Zhu, Lingshan wrote: > > > On 11/14/2023 4:27 PM, Michael S. Tsirkin wrote: > > On Tue, Nov 14, 2023 at 03:34:32PM +0800, Zhu, Lingshan wrote: > > > > > So I can't > > > > > believe it has good performance overall. Logging via IOMMU or using > > > > > shadow virtqueue doesn't need any extra PCI transactions at least. > > > > On the other hand they have an extra CPU cost. Personally if this is > > > > coming from a hardware vendor, I am inclined to trust them wrt PCI > > > > transactions. But anyway, discussing this at a high level theoretically > > > > is pointless - whoever bothers with actual prototyping for performance > > > > testing wins, if no one does I'd expect a back of a napkin estimate > > > > to be included. > > > if so, Intel has released productions implementing these interfaces years > > > ago, > > > see live migration in 4.1. IFCVF vDPA Implementation, > > > https://doc.dpdk.org/guides-21.11/vdpadevs/ifc.html > > > and > > That one is based on shadow queue, right? Which I think this shows > > is worth supporting. > Yes, it is shadow virtqueue, I assume this is already mostly done, > do you see any gaps we need to address in our series that we should work on? > > Thanks There were a ton of comments posted on your series. > > > > > But I still believe we are here try our best to work out an industrial spec > > > with better quality, to serve broad interest. This is not competition > > > between companies, > > > and the spec is not a FIFO, not like a early bird can catch all the worm. This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: virtio-comment-subscribe@lists.oasis-open.org Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org List help: virtio-comment-help@lists.oasis-open.org List archive: https://lists.oasis-open.org/archives/virtio-comment/ Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists Committee: https://www.oasis-open.org/committees/virtio/ Join OASIS: https://www.oasis-open.org/join/