From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "Tao, Zhe" <zhe.tao@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] i40e: add link flow control support for FVL
Date: Fri, 30 Oct 2015 05:13:03 +0000 [thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F8D0D67B@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1446181055-28611-1-git-send-email-zhe.tao@intel.com>
> -----Original Message-----
> From: Tao, Zhe
> Sent: Friday, October 30, 2015 12:58 PM
> To: dev@dpdk.org
> Cc: Tao, Zhe; Wu, Jingjing
> Subject: [dpdk-dev][PATCH v3] i40e: add link flow control support for FVL
>
> Feature Add: Rx/Tx flow control support for the i40e
>
> All the Rx/Tx LFC enable/disable operation is done by the F/W, so PMD driver
> need to use the Set PHY Config AD command to trigger the PHY to do the
> auto-negotiation, after the Tx/Rx pause ability is negotiated, the F/W will
> help us to set the related LFC enable/disable registers.
> PMD driver also need to configure the related registers to control how often
> to send the pause frame and what the value in the pause frame.
>
> Signed-off-by: Zhe Tao <zhe.tao@intel.com>
> ---
>
Acked-by: Jingjing Wu <jingjing.wu@intel.com>
> PATCH V1: add the LFC support for i40e
>
> PATCH v2: move the LFC parameters init to the i40e_pf_parameter_init
>
> PATCH v3: update the release note
>
> doc/guides/rel_notes/release_2_2.rst | 4 +
> drivers/net/i40e/i40e_ethdev.c | 170
> ++++++++++++++++++++++++++++++++++-
> drivers/net/i40e/i40e_ethdev.h | 12 +++
> 3 files changed, 183 insertions(+), 3 deletions(-)
next prev parent reply other threads:[~2015-10-30 5:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 5:52 [dpdk-dev] [PATCH] " Zhe Tao
2015-10-27 3:43 ` Zhang, Helin
2015-10-29 12:56 ` [dpdk-dev] [PATCH v2] " Zhe Tao
2015-10-29 13:18 ` Wu, Jingjing
2015-10-30 4:57 ` [dpdk-dev] [PATCH v3] " Zhe Tao
2015-10-30 5:13 ` Wu, Jingjing [this message]
2015-10-30 7:28 ` Zhang, Helin
2015-10-30 14:19 ` Thomas Monjalon
2015-10-30 14:22 ` Thomas Monjalon
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=9BB6961774997848B5B42BEC655768F8D0D67B@SHSMSX104.ccr.corp.intel.com \
--to=jingjing.wu@intel.com \
--cc=dev@dpdk.org \
--cc=zhe.tao@intel.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).