From: Saravana Kumar <maheshmcc39@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Regarding mbuf allocation/free in secondary process
Date: Tue, 9 Feb 2016 23:43:19 -0800 [thread overview]
Message-ID: <CAA=abZ8MgkbsDvBfZxo8SzXdeM+0VNFWtWRkh5SBDptnBvS+kQ@mail.gmail.com> (raw)
Hi DPDK community,
I'd like to have DPDK NIC IO operations in (primary) process and
execution logic in (secondary) processes.
Primary process pushes NIC Rx mbufs to Secondary process through S/W ring
Seconary process allocates mbuf for Tx path and pushes down to Primary
process for NIC Tx
I have few doubts here:
1. If Secondary process dies because of SIGKILL then how can the mbufs
allocated in Secondary process can be freed.
If it is normal signals like SIGINT/SIGTERM then we can be catch
those and free in those respective signal handlers
2. Secondary process needs to poll on the S/W ring. This can consume 100% cpu.
Is there a way to avoid polling in secondary process for Rx path
Thanks
Sara
next reply other threads:[~2016-02-10 7:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 7:43 Saravana Kumar [this message]
2016-02-10 10:01 ` Bruce Richardson
2016-02-10 10:14 ` Saravana Kumar
2016-02-10 17:50 ` Lawrence MacIntyre
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='CAA=abZ8MgkbsDvBfZxo8SzXdeM+0VNFWtWRkh5SBDptnBvS+kQ@mail.gmail.com' \
--to=maheshmcc39@gmail.com \
--cc=dev@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).