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 0/4] correctly allocate ring resource
Date: Fri,  8 Feb 2019 17:47:49 +0900	[thread overview]
Message-ID: <201902080847.x188lr06021607@imss03.silk.ntt-tx.co.jp> (raw)

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

>From 18.08.1, there is a problem that ring status is not shown
correctly when adding ring second time. 
It is because how to handle delete ring request from user is wrong. 
To resolve, this patch provides the following for spp_nfv
- Replace handling of delete ring request with rte_eth_dev_stop() and 
  rte_eth_dev_close()
- Add existence check of DPDK port when adding ring

This patch series also provides fix for spp_vf and spp_pcap because 
a problem which is caused by incorrect allocation of ring resource exists..

Note: this patch set relies on another patch set 
"introduce new feature SPP PCAP".

Hideyuki Yamashita (4):
  shared: fix trying to create ring already exist
  spp_nfv: fix incorrect deleting for ring port
  spp_vf: fix trying to create ring already exist
  spp_pcap: fix trying to create ring already exist

 src/nfv/commands.h              |  3 ++-
 src/pcap/spp_proc.c             | 17 ++++++++++++++++-
 src/shared/secondary/add_port.c | 21 ++++++++++++++++-----
 src/vf/common/spp_proc.c        | 17 ++++++++++++++++-
 4 files changed, 50 insertions(+), 8 deletions(-)

-- 
2.17.1

             reply	other threads:[~2019-02-08  8:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08  8:47 x-fn-spp [this message]
2019-02-13  7:29 ` 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=201902080847.x188lr06021607@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).