All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Shahaf Shuler <shahafs@mellanox.com>
Cc: ferruh.yigit@intel.com, dev@dpdk.org
Subject: Re: [PATCH] doc: update release notes for mlx5 driver
Date: Mon, 16 Oct 2017 12:15:57 +0200	[thread overview]
Message-ID: <65593852.KTLWt7s17m@xps> (raw)
In-Reply-To: <20171016052329.60921-1-shahafs@mellanox.com>

16/10/2017 07:23, Shahaf Shuler:
> --- a/doc/guides/rel_notes/release_17_11.rst
> +++ b/doc/guides/rel_notes/release_17_11.rst
> @@ -165,6 +165,19 @@ New Features
>    checksums, and doesn't update checksums for output packets.
>    Additionally, the GSO library doesn't process IP fragmented packets.
>  
> +* **Updated mlx5 driver.**
> +
> +  Updated the mlx5 driver including the following changes:
> +
> +   * Enabled PMD to run on top of upstream linux kernel and rdma-core libs.
> +     By that removed the dependency on specific Mellanox OFED libraries.
> +   * Improved PMD latency performance.
> +   * Improved PMD memory footprint.
> +   * Supported vectorized Rx/Tx burst for ARMv8.
> +   * Supported secondary process.
> +   * Supported flow counters.
> +   * Supported Rx hardware timestamp offload.
> +   * Supported device removal event.
>  
>  Resolved Issues
>  ---------------

2 nitpick comments:
	- you must keep the double blank line before the title
	- better to add it near other net PMD notes

  reply	other threads:[~2017-10-16 10:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16  5:23 [PATCH] doc: update release notes for mlx5 driver Shahaf Shuler
2017-10-16 10:15 ` Thomas Monjalon [this message]
2017-10-16 13:32 ` [PATCH v2] " Shahaf Shuler
2017-10-16 19:09   ` Mcnamara, John
2017-10-21  1:08     ` 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=65593852.KTLWt7s17m@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=shahafs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.