From: "Lazarenko, Vlad (WorldQuant)" <Vlad.Lazarenko@worldquant.com>
To: "'users@dpdk.org'" <users@dpdk.org>
Subject: [dpdk-users] Multi-process recovery (is it even possible?)
Date: Wed, 28 Feb 2018 18:53:39 +0000 [thread overview]
Message-ID: <790E2AC11206AC46B8F4BB82078E34F8081E0EAB@PWSSMTEXMBX002.AD.MLP.com> (raw)
Guys,
I am looking for possible solutions for the following problems that come along with asymmetric multi-process architecture...
Given multiple processes share the same RX/TX queue(s) and packet pool(s) and the possibility of one packet from RX queue being fanned out to multiple slave processes, is there a way to recover from slave crashing (or exits w/o cleaning up properly)? In theory it could have incremented mbuf reference count more than once and unless everything is restarted, I don't see a reliable way to release those mbufs back to the pool.
Also, if spinlock is involved and either master or slave crashes, everything simply gets stuck. Is there any way to detect this (i.e. outside of data path)..?
Thanks,
Vlad
###################################################################################
The information contained in this communication is confidential, may be
subject to legal privilege, and is intended only for the individual named.
If you are not the named addressee, please notify the sender immediately and
delete this email from your system. The views expressed in this email are
the views of the sender only. Outgoing and incoming electronic communications
to this address are electronically archived and subject to review and/or disclosure
to someone other than the recipient.
###################################################################################
next reply other threads:[~2018-02-28 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 18:53 Lazarenko, Vlad (WorldQuant) [this message]
2018-03-01 8:19 ` Tan, Jianfeng
2018-03-01 14:53 ` Lazarenko, Vlad (WorldQuant)
2018-03-02 0:39 ` Tan, Jianfeng
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=790E2AC11206AC46B8F4BB82078E34F8081E0EAB@PWSSMTEXMBX002.AD.MLP.com \
--to=vlad.lazarenko@worldquant.com \
--cc=users@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).