From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eu-smtp-delivery-178.mimecast.com (eu-smtp-delivery-178.mimecast.com [207.82.80.178]) by dpdk.org (Postfix) with ESMTP id B87902B82 for ; Thu, 3 May 2018 11:59:11 +0200 (CEST) Received: from ex-uknb-01.ad.s-a-m.com (83-244-203-18.cust-83.exponential-e.net [83.244.203.18]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-66--3gyO4EMOOu0_isnSh2EdQ-1; Thu, 03 May 2018 10:59:03 +0100 Received: from EX-UKHA-01.ad.s-a-m.com ([fe80::bd21:e36b:5bf6:8ca8]) by EX-UKHA-01.ad.s-a-m.com ([fe80::bd21:e36b:5bf6:8ca8%11]) with mapi id 14.03.0361.001; Thu, 3 May 2018 10:59:01 +0100 From: Richard Nutman To: "users@dpdk.org" Thread-Topic: Requiring rte_eth_allmulticast_enable in 18.02.1 Thread-Index: AdPixVoF658s51v9Sg22KUBktjvyuw== Date: Thu, 3 May 2018 09:59:00 +0000 Message-ID: <733AB18813E3864094592CC5191B172A235BD9F9@EX-UKHA-01.ad.s-a-m.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.19.77.57] x-esetresult: clean, is OK x-esetid: 37303A29F33CD06167716A MIME-Version: 1.0 X-MC-Unique: -3gyO4EMOOu0_isnSh2EdQ-1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] Requiring rte_eth_allmulticast_enable in 18.02.1 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: , X-List-Received-Date: Thu, 03 May 2018 09:59:11 -0000 Hi all, I managed to get 18.02.1 building and working for Mellanox MLX5 PMD. I am using the Flow Director still, and previously with Mellanox 16.11_4.0 = I had no problem receiving multicast packets. With 18.02.1 I am forced to use rte_eth_allmulticast_enable to see multicas= t packets on the receive side. Question: Is this expected, or should I be just adding the MAC address of t= he flow into the whitelist ? I assume the old Flow Director code was doing this before, but somehow it l= ooks like it's stopped doing this, perhaps in being switched over to use th= e new rte_flow underneath ? Is rte_eth_allmulticast_enable, or adding the MAC addresses to whitelist re= quired, or expected to be used with the new rte_flow ? Thanks, Richard.=0A----------------------------------------------------------------= -----------------------=0AThis email has been scanned for email related thr= eats and delivered safely by Mimecast.=0AFor more information please visit = http://www.mimecast.com=0A-------------------------------------------------= --------------------------------------=0A