From: Thomas Monjalon <thomas@monjalon.net>
To: Jaeeun Ham <jaeeun.ham@ericsson.com>
Cc: "users@dpdk.org" <users@dpdk.org>,
"alialnu@nvidia.com" <alialnu@nvidia.com>,
"rasland@nvidia.com" <rasland@nvidia.com>,
"asafp@nvidia.com" <asafp@nvidia.com>
Subject: Re: I need DPDK MLX5 Probe error support
Date: Sun, 03 Oct 2021 20:44:27 +0200 [thread overview]
Message-ID: <4863204.PRUBTm44oF@thomas> (raw)
In-Reply-To: <HE1PR07MB4220A97535F07557E5800667F3AD9@HE1PR07MB4220.eurprd07.prod.outlook.com>
03/10/2021 10:10, Jaeeun Ham:
> Hi Thomas,
>
> Thank you so much for your sincere support.
> I will follow your suggestion and do my best to solve this issue.
>
> By the way, is it okay to use mlx5_core driver by different applications which have different DPDK versions?
> 0000:12:01.0 (DPDK 20.11 - mlx5_pci: unable to recognize master/representors on the multiple IB)
> 0000:12:01.1 (DPDK 20.11 - mlx5_pci: unable to recognize master/representors on the multiple IB)
> 0000:12:01.2 (DPDK 18.11 - currently used)
I think it should be OK but it is not well tested.
next prev parent reply other threads:[~2021-10-03 18:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <HE1PR07MB422057B3D4E22FB2BE882D37F3A59@HE1PR07MB4220.eurprd07.prod.outlook.com>
[not found] ` <HE1PR07MB42201B7FB0F61E6FCB39AAE9F3A79@HE1PR07MB4220.eurprd07.prod.outlook.com>
2021-09-29 11:16 ` Thomas Monjalon
2021-10-02 10:57 ` Jaeeun Ham
2021-10-03 7:51 ` Thomas Monjalon
2021-10-03 8:10 ` Jaeeun Ham
2021-10-03 18:44 ` Thomas Monjalon [this message]
2021-10-05 1:17 ` Jaeeun Ham
2021-10-05 6:00 ` Thomas Monjalon
2021-10-06 9:57 ` Jaeeun Ham
2021-10-06 10:58 ` Thomas Monjalon
[not found] ` <HE1PR07MB42208754E63C0DE2D0F0D138F3B09@HE1PR07MB4220.eurprd07.prod.outlook.com>
2021-10-06 13:19 ` Thomas Monjalon
2021-10-09 1:12 ` Jaeeun Ham
2021-10-09 1:15 ` Jaeeun Ham
2021-10-09 4:42 ` Jaeeun Ham
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=4863204.PRUBTm44oF@thomas \
--to=thomas@monjalon.net \
--cc=alialnu@nvidia.com \
--cc=asafp@nvidia.com \
--cc=jaeeun.ham@ericsson.com \
--cc=rasland@nvidia.com \
--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).