DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: John McNamara <john.mcnamara@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: update the dpdk 2.2 release notes
Date: Tue, 15 Sep 2015 15:21:52 +0200	[thread overview]
Message-ID: <2874598.qVsS3oCtQ8@xps13> (raw)
In-Reply-To: <1442322474-27380-1-git-send-email-john.mcnamara@intel.com>

2015-09-15 14:07, John McNamara:
> +* **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.
> +
> +
> +* **ixgbe: Removed burst size restriction of vector RX.**
> +
> +Fixed issue where a burst size less than 32 didn't receive anything.
> +
> +
> +* **ixgbe: Fixed issue with X550 DCB.**
> +
> +Fixed a DCB issue with x550 where for 8 TCs (Traffic Classes), if a packet
> +with user priority 6 or 7 was injected to the NIC, then the NIC would only put
> +3 packets into the queue. There was also a similar issue for 4 TCs.
> +
> +
> +* **hash: Fixed memory allocation of Cuckoo Hash key table.**
> +
> +Fixed issue where an incorrect Cuckoo Hash key table size could be calculated
> +limiting the size to 4GB.
> +
> +Fixes: 48a399119619 ("hash: replace with cuckoo hash implementation")
> +
> +
> +* **eal/linux: Fixed epoll timeout.**
> +
> +Fixed issue where the ``rte_epoll_wait()`` function didn't return when the
> +underlying call to ``epoll_wait()`` timed out.


In order to easily read the release notes, I suggest to order items logically,
starting with API (ethdev, cryptodev), EAL, drivers, libs, tools, examples.
Maybe that adding some subtitles would help.
Opinions?

  reply	other threads:[~2015-09-15 13:23 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 [this message]
2015-09-16 10:50   ` Mcnamara, John
2015-09-16 12:58     ` Thomas Monjalon
2015-09-16  8:27 ` David Marchand

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=2874598.qVsS3oCtQ8@xps13 \
    --to=thomas.monjalon@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).