From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 33406A04B2 for ; Mon, 4 May 2020 19:27:34 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 82B3A1D581; Mon, 4 May 2020 19:27:13 +0200 (CEST) Received: from userp2130.oracle.com (userp2130.oracle.com [156.151.31.86]) by dpdk.org (Postfix) with ESMTP id 556DA1D952 for ; Fri, 1 May 2020 23:20:38 +0200 (CEST) Received: from pps.filterd (userp2130.oracle.com [127.0.0.1]) by userp2130.oracle.com (8.16.0.42/8.16.0.42) with SMTP id 041LJdjH181501; Fri, 1 May 2020 21:20:37 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=mime-version : message-id : date : from : to : subject : content-type; s=corp-2020-01-29; bh=bSKklL3uN4tlCoUUdtgvQkFIG7v3O4jwYZ7xamPYwi0=; b=afgGymO5Tq1O+diKJ5JNW3IDTo8JmawwScaTrps/s7YKKinSt4tTCX0J7qWKbVM0Vucx wIEcrtbpV9Yk4qt7xEkGJgKkBPm1YD+L3OOl4b73ZitI9nMTlsYQg27qFrjfEY2uCr8G BsHNh35qn37V8k+ivnKgbly+rLJ7qu5RgnNajiTdfYRAIvrk7Djy7U7ijmfz3mN4uGXt sK44LV5ZULj6Q2AAgVAD7NWoDOV7U1skImzzNSzDCITkTjIx+tY3obEi756aTS1C6vDV XIij4IlPLbCPpsErqjEWteMsrO191p2FnZdZxRalZR5FC3bVXf5fnN83zoBP7rqb7LLb Zw== Received: from aserp3030.oracle.com (aserp3030.oracle.com [141.146.126.71]) by userp2130.oracle.com with ESMTP id 30r7f843s1-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 01 May 2020 21:20:37 +0000 Received: from pps.filterd (aserp3030.oracle.com [127.0.0.1]) by aserp3030.oracle.com (8.16.0.42/8.16.0.42) with SMTP id 041LGVg6149856; Fri, 1 May 2020 21:20:36 GMT Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by aserp3030.oracle.com with ESMTP id 30r7f50s6m-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 01 May 2020 21:20:35 +0000 Received: from abhmp0001.oracle.com (abhmp0001.oracle.com [141.146.116.7]) by aserv0121.oracle.com (8.14.4/8.13.8) with ESMTP id 041LKZCV024647; Fri, 1 May 2020 21:20:35 GMT Received: from [10.39.230.231] (/10.39.230.231) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 01 May 2020 14:20:31 -0700 USER-AGENT: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 Content-Language: en-US MIME-Version: 1.0 Message-ID: <174fe8bd-4b66-7e6b-c45e-32326f9b2b4a@oracle.com> Date: Fri, 1 May 2020 21:20:30 +0000 (UTC) From: "changchun.zhang@oracle.com" To: users@dpdk.org, cingular.alex@gmail.com X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9608 signatures=668687 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 phishscore=0 adultscore=0 spamscore=0 mlxlogscore=999 bulkscore=0 mlxscore=0 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2005010152 X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9608 signatures=668687 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 impostorscore=0 mlxlogscore=999 spamscore=0 malwarescore=0 clxscore=1011 phishscore=0 mlxscore=0 lowpriorityscore=0 suspectscore=0 adultscore=0 priorityscore=1501 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2005010152 X-Mailman-Approved-At: Mon, 04 May 2020 19:27:11 +0200 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] How does Intel I350 support RSS for double VLAN (QinQ)? X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" Hi, Does anyone know how to support the RSS for receiving packets with double VLAN or QinQ vlan (0x88A8), for I350 NIC card? In the I350 datasheet, it is mentioned: 7.4.5 A packet is defined as a VLAN/802.1q packet if its type field matches the VET. Double VLAN Support The I350 supports a mode where most of the received and sent packet have at least one VLAN tag in addition to the regular tagging which might optionally be added. This mode is used for systems where the switches add an additional tag containing switching information. Note: The only packets that may not have the additional VLAN are local packets that will not have any VLAN tag. This mode is activated by setting CTRL_EXT.EXT_VLAN bit. The default value of this bit is set according to the EXT_VLAN (bit 1) in the Initialization Control 3 EEPROM word for ports 0 to 3. See Section 6.2.26 for more information. The type of the VLAN tag used for the additional VLAN is defined in the VET.VET_EXT field. Based on above, I can use the rte_eth_dev_set_vlan_offload(port_id, ETH_VLAN_EXTEND_OFFLOAD) and rte_eth_dev_set_vlan_ether_type(port_id, ETH_VLAN_TYPE_OUTER, 0x88A8) to set the vlan extend offload and the corresponding eth type successfully. But the RSS still does not work for QinQ traffic. Can anyone have some input? Thanks,