From: yasufum.o@gmail.com
To: spp@dpdk.org, ferruh.yigit@intel.com, yasufum.o@gmail.com
Subject: [spp] [PATCH 3/3] docs: update implementation of spp_pcap
Date: Wed, 3 Jul 2019 11:25:01 +0900 [thread overview]
Message-ID: <20190703022501.23738-4-yasufum.o@gmail.com> (raw)
In-Reply-To: <20190703022501.23738-1-yasufum.o@gmail.com>
From: Yasufumi Ogawa <yasufum.o@gmail.com>
This patch is to update description and examples of spp_pcap.
Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>
---
docs/guides/design/impl/spp_pcap.rst | 156 ++++++++-------------------
1 file changed, 45 insertions(+), 111 deletions(-)
diff --git a/docs/guides/design/impl/spp_pcap.rst b/docs/guides/design/impl/spp_pcap.rst
index 8c3f624..1f93d41 100644
--- a/docs/guides/design/impl/spp_pcap.rst
+++ b/docs/guides/design/impl/spp_pcap.rst
@@ -6,139 +6,73 @@
spp_pcap
========
-The following sections provide some explanation of the code.
+This section describes implementation of ``spp_pcap``.
-Initializing
-------------
-A manager thread of ``spp_pcap`` initialize eal by ``rte_eal_init()``.
-Then each of component threads are launched by
-``rte_eal_remote_launch()``.
+Slave Main
+----------
+In ``slave_main()``, it calls ``pcap_proc_receive()`` if thread type is
+receiver, or ``pcap_proc_write()`` if the type is writer.
.. code-block:: c
/* spp_pcap.c */
- int ret_dpdk = rte_eal_init(argc, argv);
- /* Start worker threads of classifier and forwarder */
- RTE_LCORE_FOREACH_SLAVE(lcore_id) {
- g_core_info[lcore_id].core[0].num = 1;
- g_pcap_info[lcore_id].thread_no = thread_no++;
- rte_eal_remote_launch(slave_main, NULL, lcore_id);
- }
+ while ((status = spp_get_core_status(lcore_id)) !=
+ SPP_CORE_STOP_REQUEST) {
+ if (pcap_info->type == TYPE_RECIVE)
+ ret = pcap_proc_receive(lcore_id);
+ else
+ ret = pcap_proc_write(lcore_id);
+ }
+ }
-Main function of slave thread
------------------------------
+Receiving Pakcets
+-----------------
-``slave_main()`` is called from ``rte_eal_remote_launch()``.
-It call ``pcap_proc_receive()`` or ``pcap_proc_write()``
-depending on the core assignment.
-``pcap_proc_write();`` provides function for ``receive``,
-and ``pcap_proc_write();`` provides function for ``write``.
+``pcap_proc_receive()`` is for receiving packets with ``rte_eth_rx_burst``
+and sending the packets to the writer thread via ring memory by using
+``rte_ring_enqueue_bulk()``.
.. code-block:: c
/* spp_pcap.c */
- int ret = SPP_RET_OK;
- unsigned int lcore_id = rte_lcore_id();
- enum spp_core_status status = SPP_CORE_STOP;
- struct pcap_mng_info *pcap_info = &g_pcap_info[lcore_id];
-
- if (pcap_info->thread_no == 0) {
- RTE_LOG(INFO, PCAP, "Core[%d] Start recive.\n", lcore_id);
- pcap_info->type = TYPE_RECIVE;
- } else {
- RTE_LOG(INFO, PCAP, "Core[%d] Start write(%d).\n",
- lcore_id, pcap_info->thread_no);
- pcap_info->type = TYPE_WRITE;
- }
- RTE_LOG(INFO, PCAP, "Core[%d] Start.\n", lcore_id);
- set_core_status(lcore_id, SPP_CORE_IDLE);
-
- while ((status = spp_get_core_status(lcore_id)) !=
- SPP_CORE_STOP_REQUEST) {
-
- if (pcap_info->type == TYPE_RECIVE)
- ret = pcap_proc_receive(lcore_id);
- else
- ret = pcap_proc_write(lcore_id);
- if (unlikely(ret != SPP_RET_OK)) {
- RTE_LOG(ERR, PCAP, "Core[%d] Thread Error.\n",
- lcore_id);
- break;
- }
- }
-
-Receive Pakcet
---------------
-
-``pcap_proc_receive()`` is the function to realize
-receiving incoming packets. This function is called in the while loop and
-receive packets. Everytime it receves packet via ``spp_eth_rx_burst()``, then
-it enqueue those packet into the ring using ``rte_ring_enqueue_bulk()``.
-Those packets are trnsfered to ``write`` cores via the ring.
-
-
-.. code-block:: c
- /* spp_pcap.c */
- /* Receive packets */
- rx = &g_pcap_option.port_cap;
+ rx = &g_pcap_option.port_cap;
+ nb_rx = rte_eth_rx_burst(rx->ethdev_port_id, 0, bufs, MAX_PCAP_BURST);
- nb_rx = spp_eth_rx_burst(rx->dpdk_port, 0, bufs, MAX_PKT_BURST);
- if (unlikely(nb_rx == 0))
- return SPP_RET_OK;
+ /* Forward to ring for writer thread */
+ nb_tx = rte_ring_enqueue_burst(write_ring, (void *)bufs, nb_rx, NULL);
- /* Write ring packets */
- nb_tx = rte_ring_enqueue_bulk(write_ring, (void *)bufs, nb_rx, NULL);
-
- /* Discard remained packets to release mbuf */
-
- if (unlikely(nb_tx < nb_rx)) {
- for (buf = nb_tx; buf < nb_rx; buf++)
- rte_pktmbuf_free(bufs[buf]);
- }
-
- return SPP_RET_OK;
-
-
-Write Packet
-------------
+Writing Packet
+--------------
-In ``pcap_proc_write()``, it dequeue packets from ring.Then it writes to
-storage after data compression using LZ4 libraries. ``compress_file_packet``
-is the function to write packet with LZ4. LZ4 is lossless compression
-algorithm, providing compression speed > 500 MB/s per core, scalable with
-multi-cores CPU. It features an extremely fast decoder, with speed in multiple
-GB/s per core, typically reaching RAM speed limits on multi-core systems.
-Please see details in
+``pcap_proc_write()`` is for capturing packets to a file. The captured file
+is compressed with
`LZ4
<https://github.com/lz4/lz4>`_
+which is a lossless compression algorithm and providing compression
+speed > 500 MB/s per core.
.. code-block:: c
- /* Read packets */
- nb_rx = rte_ring_dequeue_bulk(read_ring, (void *)bufs, MAX_PKT_BURST,
- NULL);
- if (unlikely(nb_rx == 0))
- return SPP_RET_OK;
-
- for (buf = 0; buf < nb_rx; buf++) {
- mbuf = bufs[buf];
- rte_prefetch0(rte_pktmbuf_mtod(mbuf, void *));
- if (compress_file_packet(&g_pcap_info[lcore_id], mbuf)
- != SPP_RET_OK) {
- RTE_LOG(ERR, PCAP, "capture file write error: "
- "%d (%s)\n", errno, strerror(errno));
- ret = SPP_RET_NG;
- info->status = SPP_CAPTURE_IDLE;
- compress_file_operation(info, CLOSE_MODE);
- break;
- }
- }
- for (buf = nb_rx; buf < nb_rx; buf++)
- rte_pktmbuf_free(bufs[buf]);
- return ret;
+ nb_rx = rte_ring_dequeue_bulk(read_ring, (void *)bufs, MAX_PKT_BURST,
+ NULL);
+ for (buf = 0; buf < nb_rx; buf++) {
+ mbuf = bufs[buf];
+ rte_prefetch0(rte_pktmbuf_mtod(mbuf, void *));
+ if (compress_file_packet(&g_pcap_info[lcore_id], mbuf)
+ != SPP_RET_OK) {
+ RTE_LOG(ERR, PCAP, "capture file write error: "
+ "%d (%s)\n", errno, strerror(errno));
+ ret = SPP_RET_NG;
+ info->status = SPP_CAPTURE_IDLE;
+ compress_file_operation(info, CLOSE_MODE);
+ break;
+ }
+ }
+ for (buf = nb_rx; buf < nb_rx; buf++)
+ rte_pktmbuf_free(bufs[buf]);
--
2.17.1
prev parent reply other threads:[~2019-07-03 2:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 2:24 [spp] [PATCH 0/3] Update docs of implementation of SPP secondaries yasufum.o
2019-07-03 2:24 ` [spp] [PATCH 1/3] docs: update implementation of spp_vf yasufum.o
2019-07-03 2:25 ` [spp] [PATCH 2/3] docs: update implementation of spp_mirror yasufum.o
2019-07-03 2:25 ` yasufum.o [this message]
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=20190703022501.23738-4-yasufum.o@gmail.com \
--to=yasufum.o@gmail.com \
--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).