From: Stephen Hemminger <stephen@networkplumber.org>
To: Zhongming Qu <zhongming@luminatewireless.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] running multiple independent dpdk applications randomly locks up machines
Date: Fri, 19 Aug 2016 18:30:29 -0700 [thread overview]
Message-ID: <20160819183029.6deb8ebd@xeon-e3> (raw)
In-Reply-To: <CADc8Jcg93Zs2CrYnLqhh6uoS6P8w29osCKMDz2R0LB4GZ5M9Bg@mail.gmail.com>
On Fri, 19 Aug 2016 18:19:21 -0700
Zhongming Qu <zhongming@luminatewireless.com> wrote:
> Thanks!
>
> I did use a hard coded queue_id of 0 when initializing the rx/tx queues,
> i.e., rte_eth_rx/tx_queue_setup(). So that is a problem to solve. Will fix
> that and try again.
>
> When A and B run at the same time, this lockup problem can be explained by
> the conflicting queue usage. But the lockup happens even in the use case
> where only one dpdk process is running. That is, A and B take turns to run
> but do not run at the same time.
>
> Thanks for pointing out an alternative approach. That sounds really
> promising. A concern came up when that idea was talked over: What would
> happen if the primary process dies? Would all the secondary processes
> eventually go awry at some point? Would `--proc-type auto` solve this
> problem?
>
I haven't actually used primary/secondary model, but the recommendation
is that the primary process does nothing (or is a watchdog) so it would
be pretty much impossible to crash unless killed by malicious entity.
All the packet logic would be in the secondary.
next prev parent reply other threads:[~2016-08-20 1:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 20:32 Zhongming Qu
2016-08-19 21:03 ` Stephen Hemminger
2016-08-20 1:19 ` Zhongming Qu
2016-08-20 1:30 ` Stephen Hemminger [this message]
2016-08-26 17:55 ` Zhongming Qu
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=20160819183029.6deb8ebd@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=users@dpdk.org \
--cc=zhongming@luminatewireless.com \
/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).