Soft Patch Panel
 help / color / mirror / Atom feed
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
To: x-fn-spp@sl.ntt-tx.co.jp
Cc: ferruh.yigit@intel.com, spp@dpdk.org
Subject: Re: [spp] [PATCH v2 0/5] Introduce new feature core-sharing
Date: Wed, 13 Feb 2019 15:14:25 +0900	[thread overview]
Message-ID: <08bcc252-bf01-59c4-9313-d4a87981454a@lab.ntt.co.jp> (raw)
In-Reply-To: <201902120916.x1C9GErn025666@imss03.silk.ntt-tx.co.jp>

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

Series of patches applied. Thanks.

> 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(-)
> 


-- 
Yasufumi Ogawa
NTT Network Service Systems Labs

      reply	other threads:[~2019-02-13  6:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-12  9:16 x-fn-spp
2019-02-13  6:14 ` Yasufumi Ogawa [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=08bcc252-bf01-59c4-9313-d4a87981454a@lab.ntt.co.jp \
    --to=ogawa.yasufumi@lab.ntt.co.jp \
    --cc=ferruh.yigit@intel.com \
    --cc=spp@dpdk.org \
    --cc=x-fn-spp@sl.ntt-tx.co.jp \
    /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).