From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
To: sy.jong.choi@intel.com, spp@dpdk.org
Subject: [spp] Proposal for adding port for external management tools
Date: Thu, 29 Jun 2017 18:16:28 +0900 [thread overview]
Message-ID: <894235f1-d439-8db2-73ab-55b16a474084@lab.ntt.co.jp> (raw)
Hi, everyone,
SPP controller is a CLI tool and has no way to send a command from
remote. Considering to control SPP from a management tool like an
orchestrator, it should be needed to have another port. This patch is
adding it (called management port) to SPP for the purpose.
This patch also includes following bug fixes.
- Remove unwanted spaces from the sec command to avoid parse error.
- Add socket.SO_REUSEADDR option for avoiding 'port is already used'.
- Correct command completion.
- Fix errors in report/playback command.
Regards,
Yasufumi
--
-------------------------------------------------
Yasufumi Ogawa
NTT Network Service Systems Labs
tel: 0422(59)5776 fax: 0422(59)5653
email: ogawa.yasufumi@lab.ntt.co.jp
-------------------------------------------------
next reply other threads:[~2017-06-29 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 9:16 Yasufumi Ogawa [this message]
2017-06-29 9:19 ` Yasufumi Ogawa
2017-07-06 12:56 ` Ferruh Yigit
2017-07-07 8:22 ` 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=894235f1-d439-8db2-73ab-55b16a474084@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=spp@dpdk.org \
--cc=sy.jong.choi@intel.com \
/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).