DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	Shahaf Shuler <shahafs@mellanox.com>
Cc: nelio.laranjeiro@6wind.com, yskoh@mellanox.com,
	john.mcnamara@intel.com, dev@dpdk.org, olgas@mellanox.com
Subject: Re: [dpdk-dev] [PATCH v3 1/2] doc: update mlx PMD release notes
Date: Mon, 5 Feb 2018 17:40:01 +0000	[thread overview]
Message-ID: <ca94504d-ad34-ee59-2f36-de1bd928f1e3@intel.com> (raw)
In-Reply-To: <20180205153126.GL4256@6wind.com>

On 2/5/2018 3:31 PM, Adrien Mazarguil wrote:
> On Mon, Feb 05, 2018 at 02:31:11PM +0200, Shahaf Shuler wrote:
>> Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
> 
> With one minor nit, rdma-core plug-in compilation hasn't been accepted
> yet. Assuming it will:
> 
> Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>

Series applied to dpdk-next-net/master, thanks.


> 
>> ---
>>
>> On v3:
>>  - No change.
>>
>> On v2:
>>  - No change.
>>
>> ---
>>  doc/guides/rel_notes/release_18_02.rst | 27 +++++++++++++++++++++++++++
>>  1 file changed, 27 insertions(+)
>>
>> diff --git a/doc/guides/rel_notes/release_18_02.rst b/doc/guides/rel_notes/release_18_02.rst
>> index 689080bed..714a24388 100644
>> --- a/doc/guides/rel_notes/release_18_02.rst
>> +++ b/doc/guides/rel_notes/release_18_02.rst
>> @@ -50,6 +50,33 @@ New Features
>>    exiting. Not calling this function could result in leaking hugepages, leading
>>    to failure during initialization of secondary processes.
>>  
>> +* **Updated mlx5 driver.**
>> +
>> +  Updated the mlx5 driver including the following changes:
>> +
>> +  * Enabled compilation as a plugin, thus removed the mandatory dependency with rdma-core.
>> +    With the special compilation, the rdma-core libraries will be loaded only in case
>> +    Mellanox device is being used. For binaries creation the PMD can be enabled, still not
>> +    requiring from every end user to install rdma-core.
>> +  * Improved multi-segment packet performance.
>> +  * Changed driver name to use the PCI address to be compatible with OVS-DPDK APIs.
>> +  * Extended statistics for physical port packet/byte counters.
>> +  * Supported IPv4 time-to-live filter.
>> +  * Converted to the new offloads API.
>> +  * Supported device removal check operation.
>> +
>> +* **Updated mlx4 driver.**
>> +
>> +  Updated the mlx4 driver including the following changes:
>> +
>> +  * Enabled compilation as a plugin, thus removed the mandatory dependency with rdma-core.
>> +    With the special compilation, the rdma-core libraries will be loaded only in case
>> +    Mellanox device is being used. For binaries creation the PMD can be enabled, still not
>> +    requiring from every end user to install rdma-core.
>> +  * Improved data path performance.
>> +  * Converted to the new offloads API.
>> +  * Supported device removal check operation.
>> +
>>  * **Added the ixgbe ethernet driver to support RSS with flow API.**
>>  
>>    Rte_flow actually defined to include RSS, but till now, RSS is out of
>> -- 
>> 2.12.0
>>
> 

  reply	other threads:[~2018-02-05 17:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-01 11:45 [dpdk-dev] [PATCH " Shahaf Shuler
2018-02-01 11:45 ` [dpdk-dev] [PATCH 2/2] doc: update mlx5 required OFED version Shahaf Shuler
2018-02-04  7:06 ` [dpdk-dev] [PATCH v2 1/2] doc: update mlx PMD release notes Shahaf Shuler
2018-02-05 12:31   ` [dpdk-dev] [PATCH v3 " Shahaf Shuler
2018-02-05 13:12     ` Nélio Laranjeiro
2018-02-05 15:31     ` Adrien Mazarguil
2018-02-05 17:40       ` Ferruh Yigit [this message]
2018-02-05 12:31   ` [dpdk-dev] [PATCH v3 2/2] doc: update mlx5 required OFED version Shahaf Shuler
2018-02-05 13:12     ` Nélio Laranjeiro
2018-02-05 15:31     ` Adrien Mazarguil
2018-02-04  7:08 ` [dpdk-dev] [PATCH v2 2/2] doc: update mlx PMD " Shahaf Shuler
2018-02-05  7:44   ` Nélio Laranjeiro

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=ca94504d-ad34-ee59-2f36-de1bd928f1e3@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=nelio.laranjeiro@6wind.com \
    --cc=olgas@mellanox.com \
    --cc=shahafs@mellanox.com \
    --cc=yskoh@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).