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 113ABA04B5 for ; Mon, 14 Dec 2020 06:33:13 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 6516A2BBD; Mon, 14 Dec 2020 06:33:11 +0100 (CET) Received: from mx0b-00000d04.pphosted.com (mx0b-00000d04.pphosted.com [148.163.153.235]) by dpdk.org (Postfix) with ESMTP id D8E532B9C for ; Mon, 14 Dec 2020 06:33:09 +0100 (CET) Received: from pps.filterd (m0102894.ppops.net [127.0.0.1]) by mx0a-00000d04.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 0BE5QoOu022405 for ; Sun, 13 Dec 2020 21:33:06 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stanford.edu; h=mime-version : references : in-reply-to : from : date : message-id : subject : to : cc : content-type; s=pps05272020; bh=f9z7UCyRttxJp+9qNUA0iv7QDlbj12HMtCUxAtV4cwI=; b=TNnfjAi83D0TSGo3/34hkck6Kf1sXtWdpO2ZfgmAKIW4wcKZxCQjiu2ukfLfr53jAf/5 8RdZbXCdQeidBMNlFq0J6DK6KndDKrQ4X+zMX5hmRDXMRnzZPfTQKew5O8/FSDEVPClf Z9391KmteqBdm80rALjBEwLUXz/vMJLSy7W+uy5pkjm/LLTiYzOhVbeNGpkiTM66S7h2 J4cclUzVAXPqoDnDP+5EsMQJ2qdwIS6gKzSL3XJ6uqaTC/6HYkci0UrIcX7+fxFF8jBy KlFnOXHym/zjF72vgOuwoewosldHzMScHk6fCcpt6TI3duKetb4+x1XlPygdXHGyb8rT GQ== Received: from mx0b-00000d03.pphosted.com (mx0b-00000d03.pphosted.com [148.163.153.234]) by mx0a-00000d04.pphosted.com with ESMTP id 35cus2vh11-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Sun, 13 Dec 2020 21:33:06 -0800 Received: from pps.filterd (m0206578.ppops.net [127.0.0.1]) by mx0a-00000d03.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 0BE5VdSk007042 for ; Sun, 13 Dec 2020 21:33:05 -0800 Received: from mx0a-00000d06.pphosted.com (mx0a-00000d06.pphosted.com [148.163.135.119]) by mx0a-00000d03.pphosted.com with ESMTP id 35cvw25cys-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Sun, 13 Dec 2020 21:33:05 -0800 Received: from pps.filterd (m0167934.ppops.net [127.0.0.1]) by mx0a-00000d06.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 0BE5V2KV015094 for ; Sun, 13 Dec 2020 21:33:04 -0800 Received: from smtp.stanford.edu (smtp5.stanford.edu [171.67.219.71]) by mx0a-00000d06.pphosted.com with ESMTP id 35cv5e1e8t-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Sun, 13 Dec 2020 21:33:04 -0800 Received: from mail-ot1-f41.google.com (mail-ot1-f41.google.com [209.85.210.41]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: gerryw) by smtp.stanford.edu (Postfix) with ESMTPSA id 40F6F140F0A for ; Sun, 13 Dec 2020 21:33:04 -0800 (PST) Received: by mail-ot1-f41.google.com with SMTP id j20so10155487otq.5 for ; Sun, 13 Dec 2020 21:33:04 -0800 (PST) X-Gm-Message-State: AOAM531wdfqrqv54ZnBoBmo1a8/s1CDChUzHFjzvNlqCblPRbPIUkzF8 RMfByWmXU0H/i62wVo3cJIQLGdzYEho+0HBlsko= X-Google-Smtp-Source: ABdhPJyoSwBtTPdCJ3cFNdzS4UiZwdqDeSzozcxwqc7LCErNi2QKWdw+WHxy7uAgZRKYFZumGCLt7xqsEEI9B8ctObM= X-Received: by 2002:a05:6830:110b:: with SMTP id w11mr15677573otq.285.1607923983654; Sun, 13 Dec 2020 21:33:03 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Gerry Wan Date: Sun, 13 Dec 2020 21:32:53 -0800 X-Gmail-Original-Message-ID: Message-ID: To: Raslan Darawsheh Cc: "users@dpdk.org" x-proofpoint-stanford-dir: outbound X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2020-12-13_08:2020-12-11, 2020-12-13 signatures=0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.343, 18.0.737 definitions=2020-12-13_08:2020-12-11, 2020-12-13 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0 phishscore=0 clxscore=1015 priorityscore=1501 impostorscore=0 lowpriorityscore=0 mlxlogscore=999 adultscore=100 malwarescore=0 mlxscore=0 spamscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2012140042 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] Enable MLX5 driver v20.11 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" I've found that linking with static libraries will fix this problem, but using shared libraries continues to successfully build but at runtime will not find any ports despite having devices bound to DPDK compatible drivers. Perhaps I am linking against library executables from the old DPDK version? If this is likely the case, how can I fix this to work with shared libraries? On Sun, Dec 13, 2020 at 1:04 PM Gerry Wan wrote: > OK, I was able to build it this way. > However, it seems that it still does not solve my problem where the > application detects no ports available. I am building it outside the > development kit using Make. It appears the same issue happens with the > provided sample applications. If I compile the "skeleton" sample > application with make, running it will error saying no ports available. If > I compile it using meson (meson configure -Dexamples=skeleton) and then run > it through .//examples/dpdk-skeleton it works fine. How can I > compile the applications outside of the development kit? The current > documentation says this should still be possible using make as before. > > On Sun, Dec 13, 2020 at 3:31 AM Raslan Darawsheh > wrote: > >> Starting OFED 5.1 it stopped the support for MLX4 pmd >> >> And seems that you have some libmlx4 under your local lib dir, >> >> In the meanwhile what you can do when doing ninja is to disable mxl4 >> compilation: >> >> >> >> meson build -D disable_driver=net/mlx4; ninja -C build >> >> >> >> Kindest regards, >> >> Raslan Darawsheh >> >> >> >> *From:* Gerry Wan >> *Sent:* Sunday, December 13, 2020 1:25 PM >> *To:* Raslan Darawsheh >> *Cc:* users@dpdk.org >> *Subject:* Re: [dpdk-users] Enable MLX5 driver v20.11 >> >> >> >> Thanks, >> >> I updated my MLNX_OFED to 5.1-2.5.8.0, which was tested against for this >> DPDK release. >> >> To install, I ran ./mlnxofedinstall --dpdk --upstream-libs --with-mft >> --with-kernel-mft >> >> then /etc/init.d/openibd restart >> Now, ninja install gives me ../drivers/net/mlx4/mlx4_glue.h:16:10: fatal >> error: infiniband/mlx4dv.h: No such file or directory >> >> >> >> What other steps am I missing? >> >> >> >> On Sun, Dec 13, 2020 at 12:35 AM Raslan Darawsheh >> wrote: >> >> Hi Gerry, >> >> Starting V20.11 the build system was switched to use meson only, >> And if you have necessary packages for MLX5 (a.k. rdma-core) it will be >> built automatically. >> >> As for your question if you still don't need to bind mlx5 driver that's >> true, its still valid. >> >> Kindest regards, >> Raslan Darawsheh >> >> > -----Original Message----- >> > From: users On Behalf Of Gerry Wan >> > Sent: Sunday, December 13, 2020 1:22 AM >> > To: users@dpdk.org >> > Subject: [dpdk-users] Enable MLX5 driver v20.11 >> > >> > Hello, >> > I am trying to update my DPDK version from 20.08 to 20.11. I am using >> the >> > mlx5 driver, and previously to enable it I had to set >> > CONFIG_RTE_LIBRTE_MLX5_PMD=y in config/common_base. In 20.11, I see >> > no >> > option to do so. I was able to build my application (and the sample >> > applications), but running rte_eth_dev_count_avail() returns 0 and >> cannot >> > find any ports. >> > >> > The steps I did to build DPDK from source were: >> > >> > $ meson build >> > >> > $ cd build >> > >> > $ sudo ninja install >> > >> > $ sudo ldconfig >> > >> > >> > Normally I would edit dpdk-20.xx/config/common_base before meson build, >> > but >> > that file is gone. >> > >> > What are the steps I need to take to enable mlx5 driver? I also recall >> that >> > I don't need to bind the mlx5 driver, is that still the case? >> > >> > Thanks >> >>