From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 54920AAEB for ; Mon, 21 May 2018 12:10:12 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id E0C34221CE; Mon, 21 May 2018 06:10:11 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 21 May 2018 06:10:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=KomeL2T5YILw24SEvrMeQaSqdz e3ZU8tlcSN3gnVIuo=; b=PqDVL/wvW1G1QxaiWHHDXG4V6uAK57OE4xAwkjdYP5 +N2bTDOG8uGX6LNzNm0kJiMWPLo96YYqTkMFaxhrjUnLhlr8gY4UhENgOv/7OamI aJChHkLC2261aABZUqaFZtR12AgLldjCoYbRn10YXANGAsknbtkGvIPNGCr+Cqb9 k= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=KomeL2 T5YILw24SEvrMeQaSqdze3ZU8tlcSN3gnVIuo=; b=LdX/gakMCJ98Wf07RlcxJR gfr7fsA66b50KFv8xKWFRCOGKu26UWVxjckFriflFzekRHR9iAExPDPwyFBj40w4 ILDL7FP3tPo7fWZGIJsEh//4iFnaET6K6D6kjBeqH4CDyalICH1WLozt+C3lHrkE 2B34sQJpnsv402pSx3kdFubP/fnQacEdAW8S290nFnNd6Q+0Kkht+evvw/E2ohRC PGau86ofbh7lWR6woRpxtU+LfhRjzSoKruEBrmzUnJykMQh20kvgL/wKtWNIRgD+ XTFJrhcXd4DjX4zmR2EuMkPGIkzIOsyR7IYV4QQkPiCixyQMbKWcM9DlZCD3RjDA == X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (236.204.154.77.rev.sfr.net [77.154.204.236]) by mail.messagingengine.com (Postfix) with ESMTPA id 1C45C1025C; Mon, 21 May 2018 06:10:09 -0400 (EDT) From: Thomas Monjalon To: Laurent Hardy Cc: Zijie Pan , dev , "beilei.xing" , "qi.z.zhang" , "helin.zhang" Date: Mon, 21 May 2018 12:10:07 +0200 Message-ID: <15428557.l5iPiH4DZL@xps> In-Reply-To: <6fc1b039-f79b-e82a-0e22-26f02a196697@6wind.com> References: <1526638447-31246-1-git-send-email-zijie.pan@6wind.com> <1752366.FEJfUWy9xN@xps> <6fc1b039-f79b-e82a-0e22-26f02a196697@6wind.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH] net/i40e: add a specific API to control the LLDP agent X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2018 10:10:12 -0000 21/05/2018 10:58, Laurent Hardy: > Hello Thomas, >=20 > On 05/21/2018 10:39 AM, Thomas Monjalon wrote: > > 21/05/2018 05:35, Zijie Pan: > >>>> Add a new API rte_pmd_i40e_set_lldp_cmd to control LLDP agent for i4= 0e. > >>>> It supports the following i40e debug lldp commands: > >>>> - start/stop of the LLDP agent. > >>>> - get local/remote of the LLDP MIB (Management Information Base= ). > >>>> > >>>> Signed-off-by: Laurent Hardy > >>>> Signed-off-by: Zijie Pan > >>> Does it mean that this feature is enabled by default in i40e devices? > >>> Should it be disabled by default? > >> The new API is just an interface to control the LLDP agent. No functio= ns of i40e call it by default. It is only used to debug LLDP of i40e device= s. For example we can add a new command for test-pmd to debug lldp of i40e = by calling rte_pmd_i40e_set_lldp_cmd(). > > There is a command to stop the LLDP agent. > > My question is to know whether this agent is running by default > > and should be disabled? > This agent is running by default. > Beside, disabling LLDP agent when using old fw (NVM 4.53 or 5.x) could=20 > have some side effects. >=20 > https://www.intel.com/content/dam/www/public/us/en/documents/specificatio= n-updates/xl710-10-40-controller-spec-update.pdf >=20 > Extracted from x710 intel spec: >=20 > "70. LLDP Disable Can Result in Incorrect Configuration of the Receive Pa= cket Buffer >=20 > Problem: > --------- > The default operation of the device is LLDP enabled. > LLDP can be disabled by an AQ command or by a custom NVM obtained from In= tel. > Disabling LLDP when using NVM 4.53 or 5.x can result in the device firmwa= re not configuring the Receive Packet Buffer according to the link mode and= flow control settings. > Implication: > ------------ > If flow control is disabled, a hang of the receive data path could occur = wherein all received packets are dropped. > If flow control is enabled, the incorrect settings could cause packet dro= ps despite the flow control, making the flow control ineffective. > Also, throughput might be sub-optimal in some cases. > Workaround: > ----------- > When using NVM 4.53 or 5.x, do one of the following: > =E2=80=A2 Do not disable LLDP or DCBx. Leave the device in default opera= tion mode. > =E2=80=A2 Use the Set Local LLDP MIB admin queue command to apply the (d= efault) DCB configuration during driver initialization and following any li= nk-up event. > When using NVM 6.01 or later, the receive data path does not hang even if= the FW LLDP is disabled." OK, interesting, thank you. I think you should add a comment in the code to explain why it is not disab= led. And later, we could consider disabling it with new firmwares. > > I mean i40e is generating LLDP packets by default? So the answer is yes, i40e generates packets silently :)