DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@6wind.com>
To: John McNamara <john.mcnamara@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: update the dpdk 2.2 release notes
Date: Wed, 16 Sep 2015 10:27:51 +0200	[thread overview]
Message-ID: <CALwxeUu00=fsnPBXx3HJPQMt+o+d=vtLaf=SUk5e+FeoeYksoA@mail.gmail.com> (raw)
In-Reply-To: <1442322474-27380-1-git-send-email-john.mcnamara@intel.com>

On Tue, Sep 15, 2015 at 3:07 PM, John McNamara <john.mcnamara@intel.com>
wrote:

> Update the DPDK 2.2 release notes with recent fixes:
>
>   7e01e3 i40e: fix base driver allocation when not using first numa node
>   5e73f4 ixgbe: remove burst size restriction of vector Rx
>   7fcd13 ixgbe: fix X550 DCB
>   d49e0f hash: fix memory allocation of cuckoo key table
>   9db649 eal/linux: fix epoll timeout
>
> Signed-off-by: John McNamara <john.mcnamara@intel.com>
> ---
>
> Authors of the above commits can you please check the associated release
> note below.
>
>
>  doc/guides/rel_notes/release_2_2.rst | 31 +++++++++++++++++++++++++++++++
>  1 file changed, 31 insertions(+)
>
> diff --git a/doc/guides/rel_notes/release_2_2.rst
> b/doc/guides/rel_notes/release_2_2.rst
> index 682f468..9604316 100644
> --- a/doc/guides/rel_notes/release_2_2.rst
> +++ b/doc/guides/rel_notes/release_2_2.rst
> @@ -8,6 +8,37 @@ New Features
>  Resolved Issues
>  ---------------
>
> +* **i40e: Fixed base driver allocation when not using first numa node.**
> +
> +Fixed i40e issue that occurred when a DPDK application didn't initialize
> ports
> +if memory wasn't available on socket 0.
> +
> +
>

Ok for me.

-- 
David Marchand

      parent reply	other threads:[~2015-09-16  8:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15 13:07 John McNamara
2015-09-15 13:21 ` Thomas Monjalon
2015-09-16 10:50   ` Mcnamara, John
2015-09-16 12:58     ` Thomas Monjalon
2015-09-16  8:27 ` David Marchand [this message]

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='CALwxeUu00=fsnPBXx3HJPQMt+o+d=vtLaf=SUk5e+FeoeYksoA@mail.gmail.com' \
    --to=david.marchand@6wind.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@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).