From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 0F724F94; Mon, 29 Oct 2018 03:01:30 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 8CFA1214E0; Sun, 28 Oct 2018 22:01:30 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sun, 28 Oct 2018 22:01:30 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=ZiUza3Ne1i138cbDC+ilwtSA1f3joPnUs9EBG9bm7K4=; b=aM7dhXsKpiDo 6qaO2QRRd7t9Q+SSSsxozg6KmXmGtbX79PeK/0+wcrNWknBgHV8OtUy/yORIXBJx zGodHAsnxDAG5Y//NifJHTEy/uIbpmLnHEwNRp1brsfx6GAxvvtbl1996nURge37 X2Nn4/bExGFVhF9e9q+UwVVjoeAR6ss= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=ZiUza3Ne1i138cbDC+ilwtSA1f3joPnUs9EBG9bm7 K4=; b=UMFcNqXqApDXl+ilz9KnUXBhyGd5VBXvgsM/FD5M507j3rvsgl4KsqUjQ 1HSadl01q3m8mgnPmjdkUpsNxpISZArfRdJ1HjmAFX0lo4I2HYDAXo2NUSVBvgXX /1MMd6Tp8Ez+vlNiV9L3ItCtGM3oEsgzrYqbeN7IM6WzQHOWUo3tKEiT5lx7/6wZ qvxnTG99XngIJLI472Qa4qLHTC2lqAYb3kqv2Ead1WMhSghYVaK1q5L5mmu+Nz69 P3GcICVCS8RIxL0bFtdfhlTjOfeh0O3kMB+NAR9tQc3mwgHmE/Dm/EvOliXWy98c cW9FQcFg0RyXNGSpoCtyujcMQW/zA== X-ME-Sender: X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 52A56E4619; Sun, 28 Oct 2018 22:01:29 -0400 (EDT) From: Thomas Monjalon To: "Zhao1, Wei" Cc: stable@dpdk.org, "Wang, Dong1" , "dev@dpdk.org" , "Zhang, Qi Z" , "Yigit, Ferruh" Date: Mon, 29 Oct 2018 03:01:35 +0100 Message-ID: <1715298.C9zz0hs5BT@xps> In-Reply-To: <3E2E5017C928014B90FD7864A64F0B5514F64677@SHSMSX103.ccr.corp.intel.com> References: <1539762086-15569-1-git-send-email-wei.zhao1@intel.com> <3E2E5017C928014B90FD7864A64F0B5514F64677@SHSMSX103.ccr.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] examples/ipv4_multicast: enable multicast promiscuous for all port X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2018 02:01:31 -0000 24/10/2018 10:50, Wang, Dong1: > Tested it with 82599 PF. > > Acked-by: Wang Dong The correct tag is probably Tested-by > From: Zhao1, Wei > > Add Wang Dong in the mailing list, he has test this patch. > > > > This example has not been enable for receiving multicast packet, so > > > it will drop multicast packet. Users must send packet with ether MAC > > > destination address the same as pf port MAC address, in order to > > > forward packet successfully, but this is an example for forwarding > > > ipv4 multicastpacket. So calling function > > > rte_eth_promiscuous_enable() or rte_eth_allmulticast_enable() can > > > enable promiscuous mode of all multicast packet. And aslo, DPDK has > > > rte API function of rte_eth_dev_set_mc_addr_list() for setting > > > specific multicast filter table for specific multicast IP address, > > > but this example do not support this configuration, so it need to be > > > enable multicast promiscuous mode instead. > > > > > > Signed-off-by: Wei Zhao Applied, thanks