Soft Patch Panel
 help / color / mirror / Atom feed
From: Yasufumi Ogawa <yasufum.o@gmail.com>
To: spp@dpdk.org, ferruh.yigit@intel.com, yasufum.o@gmail.com
Subject: [spp] [PATCH] version: 19.08
Date: Mon,  4 Nov 2019 23:18:48 +0900	[thread overview]
Message-ID: <20191104141848.30916-1-yasufum.o@gmail.com> (raw)

This patch is to update SPP to v19.08.

* Add forwarder thread in spp_primary because vhost PMD cannot be used
  from secondary from DPDK v19.11 or later. Vhost is added to
  spp_primary instead of secondary. VM or container can be connected
  with secondary via primary.

* Change SPP CLI to wait spp_primary is ready. You do not need to type
  `status` until primary is ready anymore.

* Update config params to launch spp_primary with two lcores for running
  forwarder thread as default.

* To make building container image is done in a short time, separate
  building steps into two Dockerfiles, one is for installing packages
  with apt and another one is for compiling DPDP apps from source.
  First one is not required to run each time building image if the built
  image can be retrieved from Docker Hub. So, the second Dockerfile uses
  the image on Docker Hub without running first one. If you are in
  offline, you need to run first one to have the base image locally.

* Update docs.

Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>
---
 GNUmakefile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/GNUmakefile b/GNUmakefile
index e262c87..274f709 100644
--- a/GNUmakefile
+++ b/GNUmakefile
@@ -1,7 +1,7 @@
 # SPDX-License-Identifier: BSD-3-Clause
 # Copyright(c) 2018 Nippon Telegraph and Telephone Corporation
 
-VERSION := 18.08.4
+VERSION := 19.08
 
 ifneq ($(RTE_SDK),)
 # Default target, can be overriden by command line or environment
-- 
2.13.1


                 reply	other threads:[~2019-11-04 14:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20191104141848.30916-1-yasufum.o@gmail.com \
    --to=yasufum.o@gmail.com \
    --cc=ferruh.yigit@intel.com \
    --cc=spp@dpdk.org \
    /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).