Soft Patch Panel
 help / color / mirror / Atom feed
From: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
To: ogawa.yasufumi@lab.ntt.co.jp, spp@dpdk.org, ferruh.yigit@intel.com
Subject: [spp] Cannnot add pcap PMD and  null PMD via spp.py
Date: Tue, 06 Nov 2018 20:37:16 +0900	[thread overview]
Message-ID: <201811061138.wA6Bc0ZK022308@ccmail04.silk.ntt-tx.co.jp> (raw)
In-Reply-To: <201811061118.wA6BIk7q014743@ccmail04.silk.ntt-tx.co.jp>

Hello,

I am testing spp through spp-ctl/spp.py.

I encounter error when
- adding pcap PMD
- adding null PMD
though spp.py.

When I look source code of spp_webapi.py,
it looks type is not defined for neither null PMD or pcap PMD. 

    def _validate_port(self, port):
        try:
            if_type, if_num = port.split(":")
            if if_type not in ["phy", "vhost", "ring"]: //problematic    
                raise
            int(if_num)
        except:
            raise KeyInvalid('port', port)

It is highly appreciated that someone provide resolution on this.

Thanks in advance.

BR,
Hideyuki Yamashita
NTT TechnoCross

  reply	other threads:[~2018-11-06 11:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-23 10:54 [spp] [PATCH 0/2] Fix compile error with DPDK v18.08 ogawa.yasufumi
2018-08-23 10:54 ` [spp] [PATCH 1/2] shared: remove nouse txq_flags ogawa.yasufumi
2018-08-23 10:54 ` [spp] [PATCH 2/2] makefile: ignore deprecated declarations ogawa.yasufumi
2018-11-06 11:18 ` [spp] [spp 03234] [PATCH 0/2] Fix compile error with DPDK v18.08 Hideyuki Yamashita
2018-11-06 11:37   ` Hideyuki Yamashita [this message]
2018-11-07  3:09     ` [spp] Cannnot add pcap PMD and null PMD via spp.py Yasufumi Ogawa
2018-11-06 12:26   ` [spp] [spp 03234] [PATCH 0/2] Fix compile error with DPDK v18.08 Yasufumi Ogawa
2018-11-07  0:35     ` Hideyuki Yamashita
2018-11-07  3:03       ` Yasufumi Ogawa
2018-11-07  3:30         ` [spp] [spp 03509] " Hideyuki Yamashita

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=201811061138.wA6Bc0ZK022308@ccmail04.silk.ntt-tx.co.jp \
    --to=yamashita.hideyuki@po.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).