From: ogawa.yasufumi@lab.ntt.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 0/5] Add config command
Date: Mon, 4 Feb 2019 12:11:56 +0900 [thread overview]
Message-ID: <1549249921-31638-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
`config` command is for managing default configurations of SPP CLI.
For example, you can change default command prompt `spp > ` to another
one.
List of all of configurations is referred with `config`, or list of
started with `p` is referred with `config p`.
# show all configs
spp > config
- max_secondary: "16" # The maximum number of secondary processes
- sec_nfv_nof_lcores: "1" # Default num of lcores for workers ...
- topo_size: "60%" # Percentage or ratio of topo
- sec_base_lcore: "1" # Shared lcore among secondaryes
- prompt: "spp > " # Command prompt
- sec_pcap_nof_lcores: "2" # Default num of lcores for ...
- sec_mirror_nof_lcores: "2" # Default num of lcores for ...
...
# only started with `p`
spp > config p
- prompt: "spp > " # Command prompt
To change configuration, specify key and its value.
# set prompt
Set prompt: "$ spp "
$ spp
Config params starting with `sec_` is used for options of `pri; launch`
command.
- sec_vf_nof_lcores
- sec_mirror_nof_lcores
- sec_pcap_nof_lcores
...
For instance, if secondary ID is `3` and `sec_vf_nof_lcores` is 3,
woker lcores is suggested as `3-5`, started from `3` and use three
cores.
Yasufumi Ogawa (5):
controller: add config command
controller: refactor pri launch command
controller: remove nouse check_sec_cmds
controller: add max_secondary to config
controller: change nof worker lcores configurable
src/controller/commands/pri.py | 121 ++++++++++++++++++++++++++------
src/controller/shell.py | 152 +++++++++++++++++++++++++++++------------
2 files changed, 210 insertions(+), 63 deletions(-)
--
2.7.4
next reply other threads:[~2019-02-04 3:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 3:11 ogawa.yasufumi [this message]
2019-02-04 3:11 ` [spp] [PATCH 1/5] controller: add " ogawa.yasufumi
2019-02-04 3:11 ` [spp] [PATCH 2/5] controller: refactor pri launch command ogawa.yasufumi
2019-02-04 3:11 ` [spp] [PATCH 3/5] controller: remove nouse check_sec_cmds ogawa.yasufumi
2019-02-04 3:12 ` [spp] [PATCH 4/5] controller: add max_secondary to config ogawa.yasufumi
2019-02-04 3:12 ` [spp] [PATCH 5/5] controller: change nof worker lcores configurable ogawa.yasufumi
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=1549249921-31638-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=ferruh.yigit@intel.com \
--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).