From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Shachar Beiser <shacharbe@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Adrien Mazarguil" <adrien.mazarguil@6wind.com>,
"Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v5] net/mlx5: support upstream rdma-core
Date: Mon, 18 Sep 2017 10:07:16 +0100 [thread overview]
Message-ID: <b0ec3e37-a4a7-7dfd-19ed-986c808249b6@intel.com> (raw)
In-Reply-To: <AM2PR05MB0689CB67E7069C101B3410EFC0620@AM2PR05MB0689.eurprd05.prod.outlook.com>
On 9/17/2017 8:31 AM, Shachar Beiser wrote:
>
>
>> -----Original Message-----
>> From: Ferruh Yigit [mailto:ferruh.yigit@intel.com]
>> Sent: Thursday, September 14, 2017 4:47 PM
>> To: Shachar Beiser <shacharbe@mellanox.com>; dev@dpdk.org
>> Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>; Nélio Laranjeiro
>> <nelio.laranjeiro@6wind.com>
>> Subject: Re: [dpdk-dev] [PATCH v5] net/mlx5: support upstream rdma-core
>>
>> On 9/14/2017 2:34 PM, Shachar Beiser wrote:
>>> This removes the dependency on specific Mellanox OFED libraries by
>>> using the upstream rdma-core and linux upstream community code.
>>
>> Would you mind mentioning what is the difference between "specific
>> Mellanox OFED libraries" and "upstream rdma-core"? If not in the
>> documentation, at least in mail list for interested people?
>>
>> Does it make sense to put this update into release notes?
>>
>> Thanks,
>> ferruh
>>
>
> Hi Ferruh,
>
> Both packages, rdma-core upstream & Mellanox OFED are Linux user-space packages :
> 1. Rdma-core is the Linux upstream user-space package.
> 2. Mellanox OFED is the Mellanox's Linux user-space package.
> The difference is the APIs . We shall explain that difference in the
> release notes .
The difference can be too much detail for release notes, I believe it is
good to mention in release notes the dependency requirement change, as
above commit log.
But this commit log can have the detail.
>
> -Shachar Beiser.
>
>>>
>>> ---
>>> I have squashed :
>>> [PATCH v2 3/3] “net/mlx5: fix interrupt enable return”
>>>
>> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpd
>> k
>>>
>> .org%2Fdev%2Fpatchwork%2Fpatch%2F28380%2F&data=02%7C01%7Cshach
>> arbe%40m
>>>
>> ellanox.com%7Cc79d7690cb454f8dd41508d4fb771dea%7Ca652971c7d2e4d9b
>> a6a4d
>>>
>> 149256f461b%7C0%7C0%7C636409936407431479&sdata=T5wgSUeCx1tzM9Z
>> UnBAauNt
>>> iG4djfIpOJZOj%2FWM6v4Y%3D&reserved=0
>>> into this patch
>>>
>>> a. Compile with rdma-core commit f11292efd541 ("Merge pull request
>>> #202") b. Tested with linux kernel 4.13-rc4 c. For performance testing
>>> recommended to wait till kernel 4.14
>>>
>>> Signed-off-by: Shachar Beiser <shacharbe@mellanox.com>
>>
>> <...>
>
next prev parent reply other threads:[~2017-09-18 9:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 12:23 [dpdk-dev] [PATCH v1] " Shachar Beiser
2017-08-24 13:43 ` Ferruh Yigit
2017-08-24 14:59 ` Nélio Laranjeiro
[not found] ` <CGME20170831161745eucas1p112753dbc96b3b209d303b007dda0408b@eucas1p1.samsung.com>
2017-08-31 16:17 ` Alexey Perevalov
2017-09-04 6:30 ` Shachar Beiser
2017-09-04 12:07 ` [dpdk-dev] [PATCH v2] " Shachar Beiser
2017-09-04 14:42 ` Nélio Laranjeiro
2017-09-05 13:19 ` [dpdk-dev] [PATCH v3] " Shachar Beiser
2017-09-05 13:44 ` Nélio Laranjeiro
2017-09-07 12:55 ` [dpdk-dev] [PATCH v4] " Shachar Beiser
2017-09-07 14:55 ` Nélio Laranjeiro
2017-09-14 13:34 ` [dpdk-dev] [PATCH v5] " Shachar Beiser
2017-09-14 13:47 ` Ferruh Yigit
2017-09-17 7:31 ` Shachar Beiser
2017-09-18 8:52 ` Shahaf Shuler
2017-09-18 9:07 ` Ferruh Yigit [this message]
2017-09-18 13:43 ` Shachar Beiser
2017-09-18 16:04 ` Yigit, Ferruh
2017-09-17 10:10 ` [dpdk-dev] [PATCH v6] " Shachar Beiser
2017-09-18 13:53 ` [dpdk-dev] [PATCH v7] " Shachar Beiser
2017-09-18 14:49 ` Shachar Beiser
2017-09-20 12:23 ` Nélio Laranjeiro
2017-09-20 15:48 ` Ferruh Yigit
2017-09-26 15:38 ` [dpdk-dev] [PATCH v8] " Nelio Laranjeiro
2017-09-28 15:40 ` Ferruh Yigit
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=b0ec3e37-a4a7-7dfd-19ed-986c808249b6@intel.com \
--to=ferruh.yigit@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.com \
--cc=shacharbe@mellanox.com \
/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).