From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ig0-f179.google.com (mail-ig0-f179.google.com [209.85.213.179]) by dpdk.org (Postfix) with ESMTP id 501F232A5 for ; Mon, 18 Apr 2016 10:09:13 +0200 (CEST) Received: by mail-ig0-f179.google.com with SMTP id f1so66393134igr.1 for ; Mon, 18 Apr 2016 01:09:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=Fx8UBQusj8RxiVU26OLR+021Ho2czwkZ9YgnwmouGKw=; b=qeJC/OYDOJffP9TC7zmwGUD3NBcAk304i0pwpu7xaeM/nFrPkP9VWo+DJ/ni4qRL+5 /DwvPo05jNOYXilO2zBlUzISQCNe+ev4Yd7aRT9vnErAmMDt39fSZWrlfrjKgQ7VbXxD 4NJBS8FeWJ3lFv0b4GkMM7b/1bQ4sIQzLk74A9CP/DIpt4jO37ToBeKtQhFw4n8YC2el xOkYrmyuZoo8zUGF536m8r1r6b3wtC00YDWCrM4qJKzuqAl2GJj+5AOxNgjad+RGAvcY vNbcXajn/T3sUz9Hk6fjAuCQ8RMP7j919+iINKo/7hhdB6rnqhYl7YCoTN2NGNyV4RQq +OXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=Fx8UBQusj8RxiVU26OLR+021Ho2czwkZ9YgnwmouGKw=; b=dsIvkUZdWfej+b8aafhk25mydLEETHXgdwodYt1qS/GDffzPJg2/r2PaWIRdr4UFvA GkCreSL4JYEF0jZvCP5ia/l+LTszsAD6oNWxSUNuDDq1g/cmjGKu7O2UeFhTyLI4NbSq efugzl9UmeUtGo8maFByn/82X3l2tDwFQs5Fxgt6T0Wpyr6+ZW1QfsVnDt4Q38JMtIHQ u0VBkqaTVDxtH+IuFZ/VE0278Ehcf1MJILhuH35RENBvQZbdDOJx0N9HRL46S+RKOk0z aPFYaYZCZSYvVpZvHq02Tye/A6MTsOtqsg9NFeb7FoCIBh/3oi7PDkxOVPegj7DjrM98 ZQ1Q== X-Gm-Message-State: AOPr4FUozgL1pCxn/8CZpYVJwMVX2dXiR+3SmDJyjQZjeqpEaiiuWn28edVlhXp2DrdbTSB/aUkQHvVtRrn3gw== X-Received: by 10.50.55.6 with SMTP id n6mr8985349igp.60.1460966952621; Mon, 18 Apr 2016 01:09:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.33.144 with HTTP; Mon, 18 Apr 2016 01:08:53 -0700 (PDT) In-Reply-To: References: From: Andriy Berestovskyy Date: Mon, 18 Apr 2016 10:08:53 +0200 Message-ID: To: yangbo Cc: dev@dpdk.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [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: Mon, 18 Apr 2016 08:09:13 -0000 Hi, Basically, you have to make sure you call rte_eth_tx_burst() every 100 ms in your forwarding loop. Here is such an example: const uint64_t bond_tx_cycles =3D (rte_get_timer_hz() + MS_PER_S - 1) * 100 / MS_PER_S; uint64_t cur_bond_cycles, diff_cycles; uint64_t last_bond_tx_cycles =3D 0; /* Inside your forwarding loop: */ cur_bond_cycles =3D rte_get_timer_cycles(); diff_cycles =3D cur_bond_cycles - last_bond_tx_cycles; if (diff_cycles > bond_tx_cycles) { last_bond_tx_cycles =3D cur_bond_cycles; rte_eth_tx_burst(bond_port_id, 0, NULL, 0); } There is a user@dpdk.org mailing list, please address such questions there. Regards, Andriy On Sat, Apr 16, 2016 at 11:41 AM, yangbo wrote: > 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 handl= ed with the expected latency and this may cause the link status to be incor= rectly 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. --=20 Andriy Berestovskyy