From: "Zhangkun (K)" <zhang.zhangkun@huawei.com>
To: "dev@dpdk.org" <dev@dpdk.org>,
"tomaszx.kulasek@intel.com" <tomaszx.kulasek@intel.com>
Cc: Liuyongan <liuyongan@huawei.com>,
"Chengwentao (Vintorcheng)" <chengwentao@huawei.com>,
zhouzhengwu <zhouzhengwu@huawei.com>
Subject: [dpdk-dev] LACP bond link broken chain due to the timeout
Date: Mon, 24 Jul 2017 02:46:08 +0000 [thread overview]
Message-ID: <0FCB215400789046A95ECE23C3E46C51908DBA89@DGGEMA502-MBX.china.huawei.com> (raw)
Hi, all
I use dpdk LACP bond for long time large flow test, there are LACP broken chain. The dpdk log is as follow:
Bond 1: slave id 0 distributing stopped.
Bond 1: slave id 1 distributing stopped.
Through the analysis of code , LACP protocol packets are handled by eal-intr-thread thread, at the same time, the thread will also deal with the other driver interrupt event and query the NIC card state .
And each polling thread is waiting for a long time that is leading to the switch disconnection timeout.
On the generic x86 OS server, has it been considered that the eal-intr-thread thread can 't get a timely scheduling, and that would result in LACP timeout and Link broken chain?
Or has it been considered that LACP bond would be put on a single thread, not shared with others?
reply other threads:[~2017-07-24 2:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0FCB215400789046A95ECE23C3E46C51908DBA89@DGGEMA502-MBX.china.huawei.com \
--to=zhang.zhangkun@huawei.com \
--cc=chengwentao@huawei.com \
--cc=dev@dpdk.org \
--cc=liuyongan@huawei.com \
--cc=tomaszx.kulasek@intel.com \
--cc=zhouzhengwu@huawei.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).