From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from BLU004-OMC4S31.hotmail.com (blu004-omc4s31.hotmail.com [65.55.111.170]) by dpdk.org (Postfix) with ESMTP id 8622E5398 for ; Sat, 16 Apr 2016 11:42:22 +0200 (CEST) Received: from BLU437-SMTP28 ([65.55.111.136]) by BLU004-OMC4S31.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Sat, 16 Apr 2016 02:42:22 -0700 X-TMN: [fGAt28JTmeQYqBdEsWCFrFSC2wA+kPFr] X-Originating-Email: [yangbo_588@outlook.com] Message-ID: From: yangbo Date: Sat, 16 Apr 2016 17:41:52 +0800 To: dev@dpdk.org MIME-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) X-OriginalArrivalTime: 16 Apr 2016 09:42:20.0625 (UTC) FILETIME=[45860410:01D197C4] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] About bond api lacp problem. X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Apr 2016 09:42:22 -0000 Hi, How to understand bond api comments: for LACP mode to work the rx/tx burst functions must be invoked at least = once every 100ms, otherwise the out-of-band LACP messages will not be = handled with the expected latency and this may cause the link status to = be incorrectly marked as down or failure to correctly negotiate with = peers. can any one give me example or more detail info ? I am extremely grateful for it.=