From: Asaf Penso <asafp@mellanox.com>
To: Jim Vaigl <jimv@rockbridgesoftware.com>,
'Stephen Hemminger' <stephen@networkplumber.org>
Cc: "users@dpdk.org" <users@dpdk.org>,
Kiran Vedere <kiranv@mellanox.com>,
Erez Ferber <erezf@mellanox.com>, Olga Shern <olgas@mellanox.com>
Subject: Re: [dpdk-users] DPDK on Mellanox BlueField Ref Platform
Date: Thu, 26 Sep 2019 10:59:31 +0000 [thread overview]
Message-ID: <AM6PR05MB661511C2F8B553DB378DC319C0860@AM6PR05MB6615.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <000001d5730b$bc69ea30$353dbe90$@com>
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
> -----Original Message-----
> From: users <users-bounces@dpdk.org> On Behalf Of Jim Vaigl
> Sent: Tuesday, September 24, 2019 10:11 PM
> To: 'Stephen Hemminger' <stephen@networkplumber.org>
> 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" <jimv@rockbridgesoftware.com> 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
>
>
next prev parent reply other threads:[~2019-09-26 10:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 16:31 Jim Vaigl
2019-09-24 17:18 ` Stephen Hemminger
2019-09-24 19:10 ` Jim Vaigl
2019-09-26 10:59 ` Asaf Penso [this message]
2019-09-26 19:46 ` Jim Vaigl
2019-10-04 17:35 ` Jim Vaigl
2019-10-04 18:28 ` Kiran Vedere
2019-10-07 16:52 ` Jim Vaigl
2019-10-07 17:00 ` Kiran Vedere
2019-10-07 17:02 ` Kiran Vedere
2019-10-07 18:10 ` Jim Vaigl
-- strict thread matches above, loose matches on Subject: below --
2019-09-20 19:34 Jim Vaigl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AM6PR05MB661511C2F8B553DB378DC319C0860@AM6PR05MB6615.eurprd05.prod.outlook.com \
--to=asafp@mellanox.com \
--cc=erezf@mellanox.com \
--cc=jimv@rockbridgesoftware.com \
--cc=kiranv@mellanox.com \
--cc=olgas@mellanox.com \
--cc=stephen@networkplumber.org \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).