From: "Choi, Sy Jong" <sy.jong.choi@intel.com>
To: "spp@dpdk.org" <spp@dpdk.org>
Subject: [spp] SPP PCIe hotplug changes for SPP
Date: Mon, 20 Feb 2017 08:37:00 +0000 [thread overview]
Message-ID: <697F8B1B48670548A5BAB03E8283550F36A210E7@PGSMSX108.gar.corp.intel.com> (raw)
Hi Everyone,
New Architecture for SPP to support PCIe hotplug.
Based on DPDK testpmd here are the steps you need to perform PCIe hotplug
1) Detaching : port stop, port close and then port detach
2) Attaching : port attach and then port start
In order to support PCI hotplug, we need to follow DPDK. And here are a few limitation with SPP primary secondary configuration:-
Limitation 1:-
Port information created by primary, hotplug changes port information. So attach and detaching at primary, will not update port information on secondary process.
- Now primary will attaching and detaching the port, because primary owns the port
- We need to put in place some rediscovery in secondary processes.
Limitation 2:
To update the port information on the secondary process, it require to us to reinit dpdk eal, which dpdk eal init can only be executed once.
- Multi thread will not solve the problem.
- We will use fork, so we separated the communication part and the datapath part.
The new spp primary will attach/detach port, secondary will reinit to rediscover port changes.
+----+----------+-------------------------------------------------+
| | SPP NFV | |
| +----------+ +--------------+ fork +--------------+ |
| | Parent | | Child | |
| | Comm - spp.py| | dpdk | |
| | Commands | | init | |
| | share mem to | | fwd | |
| | control child| | | |
+-------------------+--------------+-----------+--------------+---+
Code changes will be posted in the following emails.
Regards,
Choi, Sy Jong
Platform Application Engineer
next reply other threads:[~2017-02-20 8:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 8:37 Choi, Sy Jong [this message]
2017-02-23 13:21 Choi, Sy Jong
2017-02-23 17:45 ` Ferruh Yigit
2017-02-24 4:35 ` Wan, Qun
2017-03-07 8:36 Choi, Sy Jong
2017-04-25 8:02 Choi, Sy Jong
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=697F8B1B48670548A5BAB03E8283550F36A210E7@PGSMSX108.gar.corp.intel.com \
--to=sy.jong.choi@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).