Soft Patch Panel
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: ogawa.yasufumi@lab.ntt.co.jp, spp@dpdk.org
Subject: Re: [spp] [PATCH 00/15] Add SPP container tools
Date: Wed, 15 Aug 2018 16:34:30 +0100	[thread overview]
Message-ID: <f9449831-a8e2-389e-a554-8b0c1e81710a@intel.com> (raw)
In-Reply-To: <20180615083754.20220-1-ogawa.yasufumi@lab.ntt.co.jp>

On 6/15/2018 9:37 AM, ogawa.yasufumi@lab.ntt.co.jp wrote:
> From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
> 
> This series of patches is to add SPP container. It consists of build
> tool and app container launcher scripts.
> 
> Build tool is for creating container image and install DPDK and
> applications on the image. It also includes Dockerfiles of several
> versions of DPDK and Ubuntu.
> 
> App container scripts for launching app container with simple command
> line interfaces.
> 
> 
> Yasufumi Ogawa (15):
>   tools/sppc: add SPP container build tool
>   tools/sppc: add dockerfiles for DPDK
>   tools/sppc: add dockerfiles for pktgen
>   tools/sppc: add dockerfiles for SPP
>   tools/sppc: add spp-primary app continer
>   tools/sppc: add spp-nfv app continer
>   tools/sppc: add spp-vm app continer
>   tools/sppc: add l2fwd app continer
>   tools/sppc: add testpmd app continer
>   tools/sppc: add l3fwd app continer
>   tools/sppc: add pktgen app continer
>   tools/sppc: add load-balancer app continer
>   tools/sppc: add helloworld app continer
>   tools/sppc: add helper script for build
>   tools/sppc: add spp launcher script

Series applied, thanks.

      parent reply	other threads:[~2018-08-15 15:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15  8:37 ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 01/15] tools/sppc: add SPP container build tool ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 02/15] tools/sppc: add dockerfiles for DPDK ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 03/15] tools/sppc: add dockerfiles for pktgen ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 04/15] tools/sppc: add dockerfiles for SPP ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 05/15] tools/sppc: add spp-primary app continer ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 06/15] tools/sppc: add spp-nfv " ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 07/15] tools/sppc: add spp-vm " ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 08/15] tools/sppc: add l2fwd " ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 09/15] tools/sppc: add testpmd " ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 10/15] tools/sppc: add l3fwd " ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 11/15] tools/sppc: add pktgen " ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 12/15] tools/sppc: add load-balancer " ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 13/15] tools/sppc: add helloworld " ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 14/15] tools/sppc: add helper script for build ogawa.yasufumi
2018-06-15  8:37 ` [spp] [PATCH 15/15] tools/sppc: add spp launcher script ogawa.yasufumi
2018-08-15 15:34 ` Ferruh Yigit [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=f9449831-a8e2-389e-a554-8b0c1e81710a@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=ogawa.yasufumi@lab.ntt.co.jp \
    --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).