From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Long Li <longli@microsoft.com>,
jgg@nvidia.com
Cc: dev@dpdk.org, andrew.rybchenko@oktetlabs.ru, stephen@networkplumber.org
Subject: Re: [PATCH] net/mana: fix dependencies
Date: Mon, 10 Oct 2022 09:18:48 +0100 [thread overview]
Message-ID: <57f682bf-5833-e31f-4ec8-4b9ec53d55ee@amd.com> (raw)
In-Reply-To: <7571124.lvqk35OSZv@thomas>
On 10/9/2022 3:03 PM, Thomas Monjalon wrote:
> Long,
>
> For the reasons below, we should not have merged the MANA PMD in DPDK 22.11.
> We must not assume dependencies until they are upstream.
> This is a red flag on the PMD, a revert is possible.
>
I missed that dependencies are not ready :(
What do you think to update the MAINTAINERS file like following until
all dependencies met:
-Microsoft mana
+Microsoft mana - EXPERIMENTAL
perhaps add similar not to 'doc/guides/nics/mana.rst' to highlight the same?
They can be updated back in the future when dependencies met.
> Jason,
>
> Please could you tell us what is the expected date of release
> of the MANA support in Linux and rdma-core?
>
>
> 09/10/2022 15:53, Thomas Monjalon:
> [...]
>> The libibverbs was not detected through pkg-config.
>> The method dependency() needs to be used first.
>>
>> The support in rdma-core and Linux is not released yet,
>> so the documentation is updated.
>
> [...]
>> - The minimum required version of rdma-core with libmana is v43.
>> +
>> + The support of MANA is not merged in rdma-core 42.
>>
>> - **Kernel modules**
>>
>> @@ -56,6 +56,8 @@ and must be installed separately:
>> - mana_ib: InifiniBand device driver.
>> - ib_uverbs: user space driver for verbs (entry point for libibverbs).
>>
>> + The support of MANA is planned in Linux 6.2.
>
>
>
next prev parent reply other threads:[~2022-10-10 8:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 13:53 Thomas Monjalon
2022-10-09 14:03 ` Thomas Monjalon
2022-10-09 14:08 ` Jason Gunthorpe
2022-10-10 18:53 ` Long Li
2022-10-10 19:55 ` Thomas Monjalon
2022-10-10 20:20 ` Long Li
2022-10-10 8:18 ` Ferruh Yigit [this message]
2022-10-09 14:18 ` Thomas Monjalon
2022-10-10 21:58 ` Thomas Monjalon
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=57f682bf-5833-e31f-4ec8-4b9ec53d55ee@amd.com \
--to=ferruh.yigit@amd.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=jgg@nvidia.com \
--cc=longli@microsoft.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).