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 D7A69A2F67 for ; Fri, 4 Oct 2019 19:35:34 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 0768A1C299; Fri, 4 Oct 2019 19:35:34 +0200 (CEST) Received: from mail-qt1-f173.google.com (mail-qt1-f173.google.com [209.85.160.173]) by dpdk.org (Postfix) with ESMTP id 7BBE31C209 for ; Fri, 4 Oct 2019 19:35:32 +0200 (CEST) Received: by mail-qt1-f173.google.com with SMTP id c3so9587156qtv.10 for ; Fri, 04 Oct 2019 10:35:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rockbridgesoftware-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=exTXPagmpyQojok26zswyxXTMtlK6KgIHBzAjIqpoew=; b=2CfVrdHUENHw2QNd0P766X9hEwdLKmLR5xI1BJj1m9eNb+Ab9Ugq2vRRF91aCy6d50 eq1cRQzpM3BUGy9qUwT9/iQ9JyJfXBf1vmvxYEm2Ifl5rlhHt72NBoiqIPGf2dUrEf1W n+hXOk3yIAQJq/KZbihGwaigaP4Y/Y2pHa1caQheM1n7MEyDva03Xl9uK8YzqFrnWgQG uIPnJ4mDHJRC/MXlAdNg0riIYzH8M5iHpcqpHqVvg4Zn/pcfqDKDcJOZvTtHlWZOk/Rv MqMnmn8yQDyqXWQyKEZZm411XMk80rL/VcEsk7kwFHsCzulQ0les9M9WJMPafN3rY/uA 06qg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=exTXPagmpyQojok26zswyxXTMtlK6KgIHBzAjIqpoew=; b=QB+Vvr/04QDASXOsrRMIWOyoLRjkMK9h7DoxWBHlynU5eBteYnsPhaozd8W5VuxwMk af0S5BQLHe1Q3fS7Ipae16rRJVsoiMd114QN7a7TTMEzqFBoG4GPMi7+0k4998g32dQV qndCT75I4JF6GfKuebnf0QOCdm/2h3UDnM0UNb7yljobEykYBK+XtcM1J/8BWQum6c3G NOdKDhgxAhs2OI+j+w1xen5C6NyQ59ChJhDmQxanRA0AzfHpwYUri9ND7F2ibUF73xnF c2y1/l11Mi3cc1gRqQxaty1j2VCkbyeuUy7bpNXrAc/CQgL1sZNW1ddYO+8BkfVsKlnM glLA== X-Gm-Message-State: APjAAAVPhtWt2c+dUIJ3tM7fdHh2Oj9IqIEZo0gMJmo7DlDiqzZkHv+x XzaR7Tze4tffPCme/bmBiCfToA== X-Google-Smtp-Source: APXvYqxxPizF2xZtHMBlcHAZTOQ9cX7pDZwq0P4bNxE2+7+rDq5F1FSuT331fj5t1yKX0MMAjVYG+w== X-Received: by 2002:ac8:5043:: with SMTP id h3mr15990091qtm.99.1570210530840; Fri, 04 Oct 2019 10:35:30 -0700 (PDT) Received: from heisenberg ([45.53.204.57]) by smtp.gmail.com with ESMTPSA id c16sm3361050qkg.131.2019.10.04.10.35.28 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 04 Oct 2019 10:35:29 -0700 (PDT) From: "Jim Vaigl" To: "'Asaf Penso'" , "'Stephen Hemminger'" Cc: , "'Kiran Vedere'" , "'Erez Ferber'" , "'Olga Shern'" , "'Dan Vogel'" References: <004101d572f5$92d479d0$b87d6d70$@com> <20190924101802.273c25d9@hermes.lan> <000001d5730b$bc69ea30$353dbe90$@com> In-Reply-To: Date: Fri, 4 Oct 2019 13:35:26 -0400 Message-ID: <005001d57ada$1cc52900$564f7b00$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdVy9ZHo1HqoOeJURCCyk0eROU1EBQABnMsAAAPtiAAAU1unIAASMIgQAYqaHLA= Content-Language: en-us Subject: Re: [dpdk-users] DPDK on Mellanox BlueField Ref Platform 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" A final update on this issue. Kiran Vedere went above and beyond the call of duty: he completely reproduced my hardware setup, showed that it worked using trex to generate similar traffic to mine, and then provided me with a bundled-up .bfb of his CentOS (with updated kernel) and OFED install to try so that there would be no configuration stuff for me to mess up. Using this, I saw exactly the same crashes I had seen in my setup. After some thought, I realized the only meaningful difference was that my traffic generator and IP configuration relied on an MTU size of 9000. Once I set the MTU size down to 1500, the crashes stopped. So, the answer is clearly that I'm just not setting up for the larger MTU size. I need to start to understand how to get DPDK to manage that, but the crashing is at least understood now, and I have a way forward. Thanks very much to Kiran. Regards, --Jim -----Original Message----- From: Jim Vaigl [mailto:jimv@rockbridgesoftware.com] Sent: Thursday, September 26, 2019 3:47 PM To: 'Asaf Penso'; 'Stephen Hemminger' Cc: 'users@dpdk.org'; 'Kiran Vedere'; 'Erez Ferber'; 'Olga Shern' Subject: RE: [dpdk-users] DPDK on Mellanox BlueField Ref Platform > From: Asaf Penso [mailto:asafp@mellanox.com] > Sent: Thursday, September 26, 2019 7:00 AM > To: Jim Vaigl; 'Stephen Hemminger' > Cc: users@dpdk.org; Kiran Vedere; Erez Ferber; Olga Shern > Subject: RE: [dpdk-users] DPDK on Mellanox BlueField Ref Platform > > Hello Jim, > > Thanks for your mail. > In order for us to have a better resolution please send a mail to our support team > - support@mellanox.com > Please provide as much info about the setup, configuration etc as you can. > > In parallel, I added Erez Ferber here to assist. > > Regards, > Asaf Penso Thanks for the kind offer, Asaf. I'll take this debug effort off-line with you and Erez and post back to the list here later with any resolution so everyone can see the result. By the way, the prior suggestion of using v. 25 of rdma-core didn't pan out: the current build script just makes a local build in a subdirectory off the source tree and there's no obvious way to integrate it with the MLNX_OFED environment and the dpdk install. After resolving package dependencies to get rdma-core to build from the GitHub repo, I realized the instructions say this: --- Building This project uses a cmake based build system. Quick start: $ bash build.sh build/bin will contain the sample programs and build/lib will contain the shared libraries. The build is configured to run all the programs 'in-place' and cannot be installed. NOTE: It is not currently easy to run from the build directory, the plugins only load from the system path. --- --Jim >> -----Original Message----- >> From: users On Behalf Of Jim Vaigl >> Sent: Tuesday, September 24, 2019 10:11 PM >> To: 'Stephen Hemminger' >> Cc: users@dpdk.org >> Subject: Re: [dpdk-users] DPDK on Mellanox BlueField Ref Platform >> >> On Tue, 24 Sep 2019 12:31:51 -0400 >> "Jim Vaigl" wrote: >> >>>> Since no one has chimed in with any build/install/configure suggestion >> for >> >> the >> >> BlueField, I've spent some time debugging and thought I'd share the >> results. >> >> Building the l3fwd example application and running it as the docs >> suggest, >> >> when >> >> I try to send it UDP packets from another machine, it dumps core. >> >> >> >> Debugging a bit with gdb and printf, I can see that from inside >> >> process_packet() >> >> and processx4_step1() the calls to rte_pktmbuf_mtod() return Nil or >> >> suspicious >> >> pointer values (i.e. 0x80). The sample apps don't guard against NULL >> >> pointers >> >> being returned from this rte call, so that's why it's dumping core. >> >> >> >> I still think the problem is related to the driver config, but thought >> this >> >> might ring a bell for anyone who's had problems like this. >> >> >> >> The thing that still bothers me is that rather than seeing what I was >> >> expecting >> >> at init based on what the documentation shows: >> >> [...] >> >> EAL: probe driver: 15b3:1013 librte_pmd_mlx5 >> >> >> >> ... when rte_eal_init() runs, I'm seeing: >> >> [...] >> >> EAL: Selected IOVA mode 'PA' >> >> EAL: Probing VFIO support... >> >> >> >> This still seems wrong, and I've verified that specifying the BlueField >> >> target ID >> >> string in the make is causing "CONFIG_RTE_LIBRTE_MLX5_PMD=y" to >> appear in >> >> the .config. >> >> >> >> Regards, >> >> --Jim Vaigl >> >> 614 886 5999 >> >> >> >> >> > >> >From: Stephen Hemminger [mailto:stephen@networkplumber.org] >> >Sent: Tuesday, September 24, 2019 1:18 PM >> >To: Jim Vaigl >> >Cc: users@dpdk.org >> > >> >Subject: Re: [dpdk-users] DPDK on Mellanox BlueField Ref Platform >> >make sure you have latest version of rdma-core installed (v25). >> >The right version is not in most distros >> >> Great suggestion. I'm using the rdma-core from the MLNX_OFED 4.6-3.5.8.0 >> install. I can't figure out how to tell what version that thing includes, >> even looking at the source, since there's no version information in the >> source files, BUT I went to github and downloaded rdma-core v24 and v25 >> and neither diff cleanly with the source RPM that comes in the OFED >> install. I don't know yet if it's because this is some different version >> or if it's because Mellanox has made their own tweaks. >> >> I would hope that the very latest OFED from Mellanox would include an >> up-to-date and working set of libs/modules, but maybe you're on to >> something. It sounds like a risky move, but maybe I'll try just >> installing rdma-core from github over top of the OFED install. I have a >> fear that I'll end up with inconsistent versions, but it's worth a try. >> >> Thanks, >> --Jim