From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 6125D45932; Sat, 7 Sep 2024 22:56:03 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id EC0D3402F1; Sat, 7 Sep 2024 22:56:02 +0200 (CEST) Received: from dkmailrelay1.smartsharesystems.com (smartserver.smartsharesystems.com [77.243.40.215]) by mails.dpdk.org (Postfix) with ESMTP id D69A04026F for ; Sat, 7 Sep 2024 22:56:01 +0200 (CEST) Received: from smartserver.smartsharesystems.com (smartserver.smartsharesys.local [192.168.4.10]) by dkmailrelay1.smartsharesystems.com (Postfix) with ESMTP id 7DF5620CB7; Sat, 7 Sep 2024 22:56:01 +0200 (CEST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: virtio: RSS support capa Date: Sat, 7 Sep 2024 22:55:58 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9F6BD@smartserver.smartshare.dk> In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9F6BB@smartserver.smartshare.dk> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: virtio: RSS support capa Thread-Index: AdsAlFO+Xvl2Dh0TRUa8wR3WYhRywgA0vTtg References: <98CBD80474FA8B44BF855DF32C47DC35E9F6BB@smartserver.smartshare.dk> From: =?iso-8859-1?Q?Morten_Br=F8rup?= To: , "Chenbo Xia" , , "Ferruh Yigit" , Cc: X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org > From: Morten Br=F8rup [mailto:mb@smartsharesystems.com] > Sent: Friday, 6 September 2024 21.38 >=20 > Maxime, Chenbo, >=20 > If the virtio PMD supports RSS, it should be announced in its > capabilities. >=20 > I think this should be added to virtio_dev_info_get(): >=20 > if (host_features & (1ULL << VIRTIO_NET_F_RSS)) > dev_info->rx_offload_capa |=3D RTE_ETH_RX_OFFLOAD_RSS_HASH; Or perhaps I'm misunderstanding this capability flag. I thought it indicated RSS ability, i.e. multi-queue, effectively = shadowing rte_eth_conf.rxmode.mq_mode RTE_ETH_MQ_RX_RSS_FLAG. But maybe it doesn't. Maybe it indicates the ability to store the RSS = hash value in the mbuf. The RTE_ETH_RX_OFFLOAD_RSS_HASH flag is completely undocumented. Can someone please clarify?