Soft Patch Panel
 help / color / mirror / Atom feed
From: x-fn-spp@sl.ntt-tx.co.jp
To: ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Cc: spp@dpdk.org
Subject: [spp] [PATCH v2 0/5] Introduce new feature core-sharing
Date: Tue, 12 Feb 2019 18:16:09 +0900	[thread overview]
Message-ID: <201902120916.x1C9GErn025666@imss03.silk.ntt-tx.co.jp> (raw)

From: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>

v2:
- Add explanation on commit message of [1/5]
- Add comment on [2/5]
- Move comment block to more appropriate place 

v1:
When constructing complex configuration using spp_vf,
you need many cores.
So far, you could assign only one component per core.
This patch set introduces core-sharing feature.
By using this feature, you can assign more than two
components per core and thus can reduce core resource
consumptions.


Hideyuki Yamashita (5):
  spp_vf: remove while loop in classifier_mac
  spp_vf: change to handle multiples component
  spp_vf: move classifier component init
  spp_vf: remove to check unused cores no needed
  spp_vf: change retrieve component type

 src/vf/classifier_mac.c      | 160 +++++++++++------------------------
 src/vf/classifier_mac.h      |  11 ++-
 src/vf/common/command_dec.c  |  30 ++-----
 src/vf/common/command_proc.c |  69 +++++++--------
 src/vf/common/spp_proc.c     |  23 +++--
 src/vf/common/spp_proc.h     |  26 ++----
 src/vf/spp_vf.c              |  24 +++---
 7 files changed, 126 insertions(+), 217 deletions(-)

-- 
2.17.1

             reply	other threads:[~2019-02-12  9:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-12  9:16 x-fn-spp [this message]
2019-02-13  6:14 ` Yasufumi Ogawa

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=201902120916.x1C9GErn025666@imss03.silk.ntt-tx.co.jp \
    --to=x-fn-spp@sl.ntt-tx.co.jp \
    --cc=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).