From: "Zijie Pan" <zijie.pan@6wind.com>
To: "Thomas Monjalon" <thomas@monjalon.net>,
"Laurent Hardy" <laurent.hardy@6wind.com>
Cc: dev <dev@dpdk.org>, "beilei.xing" <beilei.xing@intel.com>,
"qi.z.zhang" <qi.z.zhang@intel.com>,
"helin.zhang" <helin.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/i40e: add a specific API to control the LLDP agent
Date: Mon, 21 May 2018 11:35:02 +0800 [thread overview]
Message-ID: <tencent_25F9DE79387EB3480E65FF66@qq.com> (raw)
In-Reply-To: <3140133.83vjVej6t9@xps>
> > Add a new API rte_pmd_i40e_set_lldp_cmd to control LLDP agent for i40e.
> > 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 <laurent.hardy@6wind.com>
> > Signed-off-by: Zijie Pan <zijie.pan@6wind.com>
>
> 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 functions of i40e call it by default. It is only used to debug LLDP of i40e devices. For example we can add a new command for test-pmd to debug lldp of i40e by calling rte_pmd_i40e_set_lldp_cmd().
next prev parent reply other threads:[~2018-05-21 3:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 10:14 Zijie Pan
2018-05-18 10:27 ` Thomas Monjalon
2018-05-21 3:35 ` Zijie Pan [this message]
2018-05-21 8:39 ` Thomas Monjalon
2018-05-21 8:58 ` Laurent Hardy
2018-05-21 10:10 ` Thomas Monjalon
2018-05-21 13:11 ` Zhang, Qi Z
2018-05-22 9:47 ` Laurent Hardy
2018-05-22 13:00 ` Zhang, Qi Z
2018-05-24 1:32 ` [dpdk-dev] [PATCH v2] " Zijie Pan
2018-05-29 5:54 ` Zhang, Helin
2018-06-14 15:58 ` Ferruh Yigit
2018-05-24 1:45 [dpdk-dev] [PATCH] " Zijie Pan
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=tencent_25F9DE79387EB3480E65FF66@qq.com \
--to=zijie.pan@6wind.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=laurent.hardy@6wind.com \
--cc=qi.z.zhang@intel.com \
--cc=thomas@monjalon.net \
/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).