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 26D72A0613 for ; Thu, 29 Aug 2019 05:12:02 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 445FA1D446; Thu, 29 Aug 2019 05:12:01 +0200 (CEST) Received: from dish-sg.nttdocomo.co.jp (dish-sg.nttdocomo.co.jp [202.19.227.74]) by dpdk.org (Postfix) with ESMTP id 224441D440 for ; Thu, 29 Aug 2019 05:11:58 +0200 (CEST) X-dD-Source: Outbound Received: from zssg-mailmd102.ddreams.local (zssg-mailmd900.ddreams.local [10.160.172.63]) by zssg-mailou102.ddreams.local (Postfix) with ESMTP id 57BC61200EE for ; Thu, 29 Aug 2019 12:11:57 +0900 (JST) Received: from t131sg-mailcc11.ddreams.local (t131sg-mailcc11.ddreams.local [100.66.31.86]) by zssg-mailmd102.ddreams.local (dDREAMS) with ESMTP id <0PWZ016CBA7XV8A0@dDREAMS> for users@dpdk.org; Thu, 29 Aug 2019 12:11:57 +0900 (JST) Received: from t131sg-mailcc11 (localhost [127.0.0.1]) by t131sg-mailcc11.ddreams.local (unknown) with SMTP id x7T3Bv2E063192 for ; Thu, 29 Aug 2019 12:11:57 +0900 Received: from zssg-mailmf105.ddreams.local (unknown [127.0.0.1]) by zssg-mailmf105.ddreams.local (Postfix) with ESMTP id 3EEC77E603B for ; Thu, 29 Aug 2019 12:11:43 +0900 (JST) Received: from zssg-mailmf105.ddreams.local (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 3D3028E6066 for ; Thu, 29 Aug 2019 12:11:43 +0900 (JST) Received: from localhost (unknown [127.0.0.1]) by IMSVA (Postfix) with SMTP id 3C5518E6064 for ; Thu, 29 Aug 2019 12:11:43 +0900 (JST) X-IMSS-HAND-OFF-DIRECTIVE: localhost:10026 Received: from zssg-mailmf105.ddreams.local (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 7E7498E6052 for ; Thu, 29 Aug 2019 12:11:42 +0900 (JST) Received: from zssg-mailua106.ddreams.local (unknown [10.160.172.62]) by zssg-mailmf105.ddreams.local (Postfix) with ESMTP for ; Thu, 29 Aug 2019 12:11:42 +0900 (JST) Received: from [10.87.198.18] (unknown [10.160.183.129]) by zssg-mailua106.ddreams.local (dDREAMS) with ESMTPA id <0PWZ00PQ5A7GR9F0@dDREAMS> for users@dpdk.org; Thu, 29 Aug 2019 12:11:40 +0900 (JST) Date: Thu, 29 Aug 2019 12:11:40 +0900 From: Hideyuki Yamashita In-reply-to: <20190814145603.D122.17218CA3@ntt-tx.co.jp_1> References: <20190809150558.D116.17218CA3@ntt-tx.co.jp_1> <20190814145603.D122.17218CA3@ntt-tx.co.jp_1> Message-id: <20190829121139.17DE.17218CA3@ntt-tx.co.jp_1> MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Mailer: Becky! ver. 2.74.02 [ja] X-TM-AS-GCONF: 00 To: "users@dpdk.org" Subject: Re: [dpdk-users] How L2 broadcast is handled under rte_flow? 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" Hello Experts, Can somebody help me? (Or many people still enjoy summer vacation?) I think it is very interesting question how NIC handles L2 broadcast when multiple queues are setup. Or are there any way(DPDK API) to set NIC to assign all rx queues when receiving L2 broadcast? Thanks in advance. BR, Hideyuki Yamashita NTT TechnoCross > Hello Experts, > > I have basic questions on how L2 broadcast is handled under rte_flow. > > [Question1] > > To which queue L2 broadcast packet will be received? > > testpmd> flow create 0 ingress pattern eth dst is 11:22:33:44:55:66 type mask 0xffff / end actions queue index 1 / end > testpmd> flow create 0 ingress pattern eth dst is 22:33:44:55:66:77 type mask 0xffff / end actions queue index 2 / end > > My expectation is both queue 1 and queue 2 receive broadcast(dst MAC is > FF:FF:FF:FF:FF:FF). > Or only default queue (queue 0 ) receive the packet? > > If we assume NIC act as switching hub and queues are ports, > broadcast packets will be flooded to all available ports. > Let us assume the situation that there exists software switch > which act like switching hub (deliver packets based on dst MAC), > and I want the function offload to NIC via rte_flow. > > [Question2] > What happens if VLAN is involved? > > My expectation is as following: > If receive broadcast packet (dst is FF:FF:FF:FF:FF:FF) for specific vlan, > all queues related to this vlan id will receive the broadcast packet. > Is my understanding correct? > > It may depends on each rte_flow implementations. > But if there is a rule in common among various NICs, I want to know.