From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-sn1nam01on0073.outbound.protection.outlook.com [104.47.32.73]) by dpdk.org (Postfix) with ESMTP id 8DC2B2C4F for ; Mon, 5 Dec 2016 20:00:48 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=SonusNetworks.onmicrosoft.com; s=selector1-sonusnet-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=xx4Be+Wv4DFgVg4pHHc8a3DX6BQ9fd5zqketlZTIvuY=; b=eVFWt1oXupEdQiXlFpyAobZcmkz12hBD0W8JK8fKIzXsHITy2Pkv5pVEOxpPwLDmGITCMQ5P4Rjatmx1gFIqG2xSU9tj5eoerJbYmM94PFHx+uNfueXIEiCb6QhKHIjGLN2BKqiVyesjQrpecZqbaW2rKwhPEifnMzw1XOqJlrs= Received: from BN3PR03MB1494.namprd03.prod.outlook.com (10.163.35.145) by BN3PR03MB1493.namprd03.prod.outlook.com (10.163.35.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.761.9; Mon, 5 Dec 2016 19:00:42 +0000 Received: from BN3PR03MB1494.namprd03.prod.outlook.com ([10.163.35.145]) by BN3PR03MB1494.namprd03.prod.outlook.com ([10.163.35.145]) with mapi id 15.01.0761.016; Mon, 5 Dec 2016 19:00:41 +0000 From: "Dey, Souvik" To: "Lu, Wenzhuo" , "dev@dpdk.org" Thread-Topic: ixgbevf: support multicast packets from PF to VF Thread-Index: AdJMwUeMIovxzxwPQU2ASbR+LZsrlAAABeeQAHZmrXAAI3HaEA== Date: Mon, 5 Dec 2016 19:00:41 +0000 Message-ID: References: <6A0DE07E22DDAD4C9103DF62FEBC090939355C77@shsmsx102.ccr.corp.intel.com> In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC090939355C77@shsmsx102.ccr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=sodey@sonusnet.com; x-originating-ip: [208.45.178.4] x-ms-office365-filtering-correlation-id: 2f64eb74-4f91-400f-accd-08d41d41028c x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:BN3PR03MB1493; x-microsoft-exchange-diagnostics: 1; BN3PR03MB1493; 7:2DHm8bWJ6HC0OpKCk/d6RBz9ix6brKelkd09ZPWr9gqxTNSJn1wEr2xygozHkNcGLjjUFH4uKfqicly3/lc4/2quw6RvA+UzUQ/nJCAdPBxT+92tUOwSBFH9Lm5OnKvj4qbclpvOMo3qsWHzgiEV1HTlu2SpiyIsB4KxFYgi80THNN9BAm/Hb+PCWRsSmNdoYGioCIT1X9BGRVMTbfTz161xhKyc9fMSrSy7A6rgDqAjndXxK34RQW/+35FlQQsTH3wBwtndzx1Z1/wyVuIIHDGBeQDOeP6x2pQfNs44WI0AidWYh3jdww3Stgzi3nYNWiPrqsEPkzkrM2BH1f/jv6lk+Dbvc8cApHqK2QdsQWVYWE5tDZ+tMgwd9U8va7VKRlrwPDEASmHbk2lZERTPj+fjXA3nICEOB8zFI805Hy185EIijbCwCfT/Efv+XN5yuOzQm7e1vSHNd+Cos4a5KQ== x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(21748063052155)(228905959029699); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6041248)(20161123555025)(20161123562025)(20161123564025)(20161123560025)(6047074)(6072148); SRVR:BN3PR03MB1493; BCL:0; PCL:0; RULEID:; SRVR:BN3PR03MB1493; x-forefront-prvs: 0147E151B5 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(7916002)(51874003)(199003)(53754006)(189002)(377454003)(77096006)(39450400002)(39410400001)(8936002)(76176999)(606004)(66066001)(50986999)(54356999)(790700001)(3846002)(102836003)(6116002)(101416001)(9686002)(9326002)(86362001)(68736007)(92566002)(99286002)(2900100001)(38730400001)(33656002)(106356001)(74316002)(105586002)(122556002)(7736002)(7846002)(7696004)(2950100002)(5660300001)(229853002)(97736004)(5001770100001)(107886002)(189998001)(3660700001)(2501003)(8676002)(76576001)(81156014)(81166006)(3900700001)(2906002)(3280700002)(39840400001)(39850400001)(6506006); DIR:OUT; SFP:1101; SCL:1; SRVR:BN3PR03MB1493; H:BN3PR03MB1494.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: sonusnet.com does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: sonusnet.com X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Dec 2016 19:00:41.6874 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 29a671dc-ed7e-4a54-b1e5-8da1eb495dc3 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR03MB1493 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] ixgbevf: support multicast packets from PF to VF 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, 05 Dec 2016 19:00:49 -0000 Hi Wenzhuo, There is nothing set with the rte_eth_dev_set_mc_addr_list and we are tryin= g to receive the NS packet which has the destination MAC set as 33 33 ff 00= 00 14. Also what I saw is that the handling of allmulticast_enable message= in the kernel has happened after 4.0 version and the PF drivers which earl= ier kernel version will not support this. How should handle those scenarios= ? In my case too I tried 2 experiments : 1. Only set the rte_eth_allmulticast_enable from the DPDK app and I p= atched the ixgbevf_pmd with our patch. The function was returning SUCCESS b= ut the NS packets were received in the application. 2. Then along with rte_eth_allmulticast_enable, I used the rte_eth_de= v_set_mc_addr_list to set the MAC 33 33 ff 00 00 14 from my app to the pmd.= After this I was successfully receiving the NS packets. But then the bigge= r question is how to automate the addition of mc_addr in rte_eth_dev_set_mc= _addr_list as in the kni we are currently not using the kni_net_set_rx_mode= () function which is called by the net_device whenever the new mc_addr is a= ssigned to the net_device. -- Regards, Souvik From: Lu, Wenzhuo [mailto:wenzhuo.lu@intel.com] Sent: Sunday, December 4, 2016 9:02 PM To: Dey, Souvik ; dev@dpdk.org Subject: RE: ixgbevf: support multicast packets from PF to VF Hi Souvik, To my opinion, rte_eth_dev_set_mc_addr_list has nothing to do with rte_eth_= allmulticast_enable. rte_eth_allmulticast_enable is enough for the multicas= t packets. I'm curious about the 1, what MAC addresses are set by rte_eth_dev_set_mc_a= ddr_list? 2, What multicast packets are sent? Thanks. Best regards Wenzhuo Lu From: Dey, Souvik [mailto:sodey@sonusnet.com] Sent: Saturday, December 3, 2016 1:28 AM To: dev@dpdk.org; Lu, Wenzhuo Subject: RE: ixgbevf: support multicast packets from PF to VF Adding wenzhuo.lu@intel.com From: Dey, Souvik Sent: Friday, December 2, 2016 12:27 PM To: 'dev@dpdk.org' > Subject: ixgbevf: support multicast packets from PF to VF Hi All, I am trying to support multicast packet over SRIOV using ke= rnel PF + DPDK VF(ixgbevf) drivers for ipv6. I am currently using 2.1 DPDK = and found that there was a patch in 16.04 for "ixgbe: support multicast pro= miscuous mode on VF". So I have backported the patch to the 2.1 DPDK but st= ill multicast packets were not coming up to the DPDK app. Then I tried to e= nable the rte_eth_dev_set_mc_addr_list and with the the packets were coming= up properly. Now I have some doubts : 1. Do we have to use both rte_eth_dev_set_mc_addr_list and rte_eth_all= multicast_enable to get the multicast packets. 2. How do we get the mc_addr_list dynamically as I don't see we are us= ing the kni_net_set_rx_mode in rte_kni. Without this the DPDK app will not = have any idea to update the mc_addr_list in the PF. 3. Is there any other patches which I should be using to get this func= tionality working. I am using : DPDK -2.1 Host kernel - 4.4 ( ubuntu) Guest kernel - 3.2 (Debian) Drivers - ixgbe ( for both pf and vf). Thanks in advance for the help and support. -- Regards, Souvik