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 868B3C001DB for ; Fri, 4 Aug 2023 14:07:23 +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 BAAAF7908A for ; Fri, 4 Aug 2023 14:07:22 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id A042F98670C for ; Fri, 4 Aug 2023 14:07:22 +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 8A3919866DE; Fri, 4 Aug 2023 14:07:22 +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 7693D9866DF for ; Fri, 4 Aug 2023 14:07:22 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: IVCvtc30Mneh_jBET9G0Gw-1 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691158038; x=1691762838; 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=vBtqQ94NA8ntaFqIdglJoTAlV0bEhfHYwalP0i8yaok=; b=Mc69MXAUMlWhEnvj/+BK3+AxEwFa6zXb7czoClZGRd/TMAmEJ/r2as6dx2zf58RKsS 8VvQCdHRdknyRwxck1PF7zI5SJ8eFX2oaPr8xi0J8uN2sqhyBw8p66Z2/BiS5TgZ/dh4 vdREOGcx2+55O/VqJ8V4oL/WwaikURSV0fNjSgsL9gkigyIMNkUYUuzAx9IZIwaEUluh Tbb0E+mCSe9i2BN0ep+Ru6Tg6G/bOczp/M57gCU8cdeQrrcQC6L55fM5tIaqUljEKkRH OSYERPdwuFsMy+BLF2cA5aVqBA1GeuFtvI7Qh367WC8Pb+pL2ct3SoLH9PA2bqHgEBTk uvHg== X-Gm-Message-State: AOJu0Yw/ICdlIiND3fWArBw9TKxJRRXOiKg82mXEEvnYvf9hSNCKbUUr bp3BBnj78EyBrAdPAsAzxWL3NrYME0MXkZCzkNUc4R5GeQ0YD35c6CfxB6Cn2MPb1KyygCumr3v n1cjmbbhmTnJ5ExqHH7pWvn2DuERJSBRdGQ== X-Received: by 2002:a2e:964e:0:b0:2b7:a72:103b with SMTP id z14-20020a2e964e000000b002b70a72103bmr1587224ljh.53.1691158038642; Fri, 04 Aug 2023 07:07:18 -0700 (PDT) X-Google-Smtp-Source: AGHT+IGV73DBG/wiv9x5Tq6EEYaF32Xovvck29p7h89Q8dzXeN9QNwt6vyZHEgQynrbShW1X8yyA8A== X-Received: by 2002:a2e:964e:0:b0:2b7:a72:103b with SMTP id z14-20020a2e964e000000b002b70a72103bmr1587201ljh.53.1691158038166; Fri, 04 Aug 2023 07:07:18 -0700 (PDT) Date: Fri, 4 Aug 2023 10:07:13 -0400 From: "Michael S. Tsirkin" To: Parav Pandit Cc: Xuan Zhuo , "virtio-dev@lists.oasis-open.org" , "jasowang@redhat.com" , "virtio-comment@lists.oasis-open.org" Message-ID: <20230804095255-mutt-send-email-mst@kernel.org> References: <1691062877.0013635-8-xuanzhuo@linux.alibaba.com> <1691129914.3255427-1-xuanzhuo@linux.alibaba.com> <1691132049.7182267-2-xuanzhuo@linux.alibaba.com> <1691135097.4908528-3-xuanzhuo@linux.alibaba.com> <20230804053958-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: Re: RE: RE: RE: [virtio-comment] RE: RE: RE: RE: [RFC] virtio-net: support access and control the member devices On Fri, Aug 04, 2023 at 12:49:04PM +0000, Parav Pandit wrote: > > > > From: Michael S. Tsirkin > > Sent: Friday, August 4, 2023 4:03 PM > > > > > > > > > At this point to have port for owner device requires creating a dedicated > > switching object, to be located sometimes side by side inside the owner, > > sometimes outside. > > > > All of these cases to be crafted, please rethink if this is _really_ needed as > > virtio object or not. > > > > > > > > > > YES. > > > > > > We can hear others. > > > > > > @Jason @Michael > > > > > > > > > Thanks > > > > > > This is so abstract, hard to have any position as I'm not sure what we are > > discussing. If some virtio devices have an integrated switch then ability to > > control the switch through virtio seems useful. > > > True, for us, at this point we do not have plan to expose virtio switch device because users are not blocked on it. If someone does though I see no reason not to - we have a variety of devices, switch would be just another one. The motivation would be the usual one for virtio - so there's one generic driver. > > Re:queues - it's not by chance that we have multiple admin queues. > > So driver can dedicate one queue to filtering commands if that's felt to be > > important. > > > Admin queue currently do not send non admin command of the device. > Would you propose admin queue for something else also for rtc or console or cryto device and indicate its role so device can understand what is coming to it. Well, I guess this switch has group members as its "ports" so maybe that makes it like an admin command. Again it's all up in the air too much to be able to judge. -- MST 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/