DPDK patches and discussions
 help / color / mirror / Atom feed
From: Remy Horton <remy.horton@intel.com>
To: dev@dpdk.org, John McNamara <john.mcnamara@intel.com>
Subject: [dpdk-dev] [PATCH v2 3/3] doc: add keepalive enhancement documentation
Date: Wed, 18 May 2016 10:30:18 +0100	[thread overview]
Message-ID: <1463563818-2249-4-git-send-email-remy.horton@intel.com> (raw)
In-Reply-To: <1463563818-2249-1-git-send-email-remy.horton@intel.com>

Signed-off-by: Remy Horton <remy.horton@intel.com>
---
 doc/guides/rel_notes/release_16_07.rst | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/doc/guides/rel_notes/release_16_07.rst b/doc/guides/rel_notes/release_16_07.rst
index f6d543c..bc269b0 100644
--- a/doc/guides/rel_notes/release_16_07.rst
+++ b/doc/guides/rel_notes/release_16_07.rst
@@ -34,6 +34,11 @@ This section should contain new features added in this release. Sample format:
 
   Refer to the previous release notes for examples.
 
+* **Added keepalive enhancements.**
+
+   Adds support for reporting LCore liveness to secondary processes and
+   support for idled CPUs.
+
 
 Resolved Issues
 ---------------
-- 
2.5.5

  parent reply	other threads:[~2016-05-18  9:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-29  5:41 [dpdk-dev] [PATCH v1 0/3] Keep-alive enhancements Remy Horton
2016-04-29  5:41 ` [dpdk-dev] [PATCH v1 1/3] eal: add new keepalive state & callback hook Remy Horton
2016-04-29  5:41 ` [dpdk-dev] [PATCH v1 2/3] examples/l2fwd-keepalive: add IPC liveness reporting Remy Horton
2016-04-29  5:41 ` [dpdk-dev] [PATCH v1 3/3] doc: add keepalive enhancement documentation Remy Horton
2016-05-17  7:30 ` [dpdk-dev] FW: [PATCH v1 0/3] Keep-alive enhancements Liu, Shucong
2016-05-18  9:30 ` [dpdk-dev] [PATCH v2 " Remy Horton
2016-05-18  9:30   ` [dpdk-dev] [PATCH v2 1/3] eal: add new keepalive states & callback hooks Remy Horton
2016-06-08  9:53     ` Thomas Monjalon
2016-05-18  9:30   ` [dpdk-dev] [PATCH v2 2/3] examples/l2fwd-keepalive: add IPC liveness reporting Remy Horton
2016-05-18  9:30   ` Remy Horton [this message]
2016-06-08  9:52     ` [dpdk-dev] [PATCH v2 3/3] doc: add keepalive enhancement documentation Thomas Monjalon
2016-06-14 10:03       ` Remy Horton
2016-06-02 13:57   ` [dpdk-dev] [PATCH v2 0/3] Keep-alive enhancements Tahhan, Maryam
2016-06-15  9:17   ` [dpdk-dev] [PATCH v3 " Remy Horton
2016-06-15  9:17     ` [dpdk-dev] [PATCH v3 1/3] eal: export keepalive state enumerations Remy Horton
2016-06-15  9:27       ` Thomas Monjalon
2016-06-15  9:32         ` Remy Horton
2016-06-15  9:17     ` [dpdk-dev] [PATCH v3 2/3] eal: add additional keepalive callbacks Remy Horton
2016-06-15  9:17     ` [dpdk-dev] [PATCH v3 3/3] examples/l2fwd-keepalive: add IPC liveness reporting Remy Horton
2016-06-15 15:25     ` [dpdk-dev] [PATCH v4 0/3] Keep-alive enhancements Remy Horton
2016-06-15 15:25       ` [dpdk-dev] [PATCH v4 1/3] eal: export keepalive state enumerations Remy Horton
2016-06-15 15:25       ` [dpdk-dev] [PATCH v4 2/3] eal: add additional keepalive callbacks Remy Horton
2016-06-15 15:25       ` [dpdk-dev] [PATCH v4 3/3] examples/l2fwd-keepalive: add IPC liveness reporting Remy Horton
2016-06-16 16:30       ` [dpdk-dev] [PATCH v4 0/3] Keep-alive enhancements 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=1463563818-2249-4-git-send-email-remy.horton@intel.com \
    --to=remy.horton@intel.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).