From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-gw.pt.net (smtp-gw.pt.net [206.210.194.15]) by dpdk.org (Postfix) with ESMTP id 09FD84C8E for ; Mon, 19 Nov 2018 16:09:23 +0100 (CET) X-ASG-Debug-ID: 1542640162-09411a0ed790990001-TfluYd Received: from mail.pt.net (mail.pt.net [206.210.194.11]) by smtp-gw.pt.net with ESMTP id l8hdZFHzotBSPWui (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 19 Nov 2018 09:09:22 -0600 (CST) X-Barracuda-Envelope-From: mit@perftech.com X-Barracuda-Effective-Source-IP: mail.pt.net[206.210.194.11] X-Barracuda-Apparent-Source-IP: 206.210.194.11 Received: from localhost (localhost [IPv6:::1]) by mail.pt.net (Postfix) with ESMTP id CDEA68403DC; Mon, 19 Nov 2018 09:09:22 -0600 (CST) Received: from mail.pt.net ([IPv6:::1]) by localhost (mail.pt.net [IPv6:::1]) (amavisd-new, port 10032) with ESMTP id Gz5mrWaND3vF; Mon, 19 Nov 2018 09:09:22 -0600 (CST) Received: from localhost (localhost [IPv6:::1]) by mail.pt.net (Postfix) with ESMTP id 71CB3842475; Mon, 19 Nov 2018 09:09:22 -0600 (CST) X-Virus-Scanned: amavisd-new at pt.net Received: from mail.pt.net ([IPv6:::1]) by localhost (mail.pt.net [IPv6:::1]) (amavisd-new, port 10026) with ESMTP id Pis8F56_snzO; Mon, 19 Nov 2018 09:09:22 -0600 (CST) Received: from mail.pt.net (mail.pt.net [206.210.194.11]) by mail.pt.net (Postfix) with ESMTP id 38B5D8403DC; Mon, 19 Nov 2018 09:09:22 -0600 (CST) Date: Mon, 19 Nov 2018 09:09:22 -0600 (CST) From: Mit Matelske To: shahafs Cc: Thomas Monjalon , dev , stephen , Yongseok Koh Message-ID: <383796151.782033.1542640162186.JavaMail.zimbra@perftech.com> In-Reply-To: References: <1203238912.103536.1542300483728.JavaMail.zimbra@perftech.com> <4060784.NMgGY7Cv01@xps> <164311280.707048.1542583391811.JavaMail.zimbra@perftech.com> MIME-Version: 1.0 X-ASG-Orig-Subj: Re: [dpdk-dev] mlx5 under FreeBSD Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailer: Zimbra 8.8.10_GA_3713 (ZimbraWebClient - GC70 (Linux)/8.8.10_GA_3041) Thread-Topic: mlx5 under FreeBSD Thread-Index: aO4fK4cZ1J0dwlDFBqqsMKaGSDlx88zAQc6AgACSe4CAAHbEwAyNroVt X-Barracuda-Connect: mail.pt.net[206.210.194.11] X-Barracuda-Start-Time: 1542640162 X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384 X-Barracuda-URL: https://smtp-gw.pt.net:443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at pt.net X-Barracuda-Scan-Msg-Size: 2328 X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.62041 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- Subject: Re: [dpdk-dev] mlx5 under FreeBSD 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, 19 Nov 2018 15:09:24 -0000 > Monday, November 19, 2018 1:23 AM, Mit Matelske: >> Subject: Re: [dpdk-dev] mlx5 under FreeBSD >> >> > 15/11/2018 17:48, Mit Matelske: >> >> Is anyone working to include support for the mlx5 PMD under FreeBSD? >> > >> > I think Stephen (Cc) looked at it. >> > >> >> I've started down this road by building Linux compatibility layers >> >> for the required Netlink and Ethtool calls in the driver, but would >> >> gladly accept help and advice from those much more knowledgeable then >> myself! > > Are you sure netlink and ioctl is all you need? > Looks like also sysfs stuff, and I am not sure what else is missing from the > DPDK eal layer, the FreeBSD has many not supported functions. No, I'm not sure of anything. I've just started focusing on this. I do know to get it to compile I had to include subsets the following includes: libmnl/libmnl.h linux/ethtool.h linux/netlink.h linux/neighbour.h linux/types.h linux/rtnetlink.h linux/pkt_cls.h linux/pkt_sched.h linux/if_ether.h linux/tc_act/tc_gact.h linux/tc_act/tc_mirred.h My initial goal is to change the DPDK code as little as possible, but that might not be be possible. You'd have a much better feel for that than me at this point. > > We haven't started to work on it because the majority of our use cases are for > Linux. I figured as much. > Nevertheless, we can help with code reviews and guidance. Once I get somewhere I will definitely take you up on that. Thanks! Mit > >> > >> > Cc also mlx5 maintainers. >> >> Thomas- >> >> Thanks for looping the correct people in! >> >> > >> >> Though not important, why did Mellanox build a PMD that relied on the >> >> kernel driver being in place unlike most other PMDs? >> > >> > Because it allows to choose which flows go to DPDK and which ones are >> > processed by the kernel. >> > Actually, you should ask why other PMDs don't have this feature ;) > > +1. > >> >> Very fair response. We actually wrote our own "shim" into the stack for all >> the relevant drivers we use to both keep the existing ifnet interfaces around >> and to pass packets to and from the stack from every interface. >> >> Your comment matches one of my co-worker's when I explained to him how >> the mlx5 driver works. >> >> Mit >>