From: Andrew Rybchenko <arybchenko@solarflare.com>
To: John McNamara <john.mcnamara@intel.com>, <dev@dpdk.org>
Cc: <marko.kovacevic@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1] doc: update release notes for 19.05
Date: Fri, 10 May 2019 17:19:33 +0300 [thread overview]
Message-ID: <ddc6c410-49f9-f10f-9c05-e4ef3ec225d3@solarflare.com> (raw)
In-Reply-To: <1557497897-63031-1-git-send-email-john.mcnamara@intel.com>
On 5/10/19 5:18 PM, John McNamara wrote:
> Fix grammar, spelling and formatting of DPDK 19.05 release notes.
>
> Signed-off-by: John McNamara <john.mcnamara@intel.com>
[snip]
> * **Updated Solarflare network PMD.**
>
> - Updated the sfc_efx driver including the following changes:
> + Updated the Solarflare ``sfc_efx`` driver with changes including:
>
> * Added support for Rx descriptor status and related API in a secondary
> process.
> * Added support for Tx descriptor status API in a secondary process.
> - * Added support for RSS RETA and hash configuration get API in a secondary
> + * Added support for RSS RETA and hash configuration API in a secondary
I've tried to highlight that secondary process can read (get) RETA table
and hash
configuration, but cannot change it (update).
> process.
> * Added support for Rx packet types list in a secondary process.
> * Added Tx prepare to do Tx offloads checks.
[snip]
Thanks,
Andrew.
next prev parent reply other threads:[~2019-05-10 14:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 14:18 John McNamara
2019-05-10 14:18 ` John McNamara
2019-05-10 14:19 ` Andrew Rybchenko [this message]
2019-05-10 14:19 ` Andrew Rybchenko
2019-05-13 8:30 ` Mcnamara, John
2019-05-13 8:30 ` Mcnamara, John
2019-05-13 19:51 ` Thomas Monjalon
2019-05-13 19:51 ` 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=ddc6c410-49f9-f10f-9c05-e4ef3ec225d3@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.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).