DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>, dev@dpdk.org
Cc: kaara.satwik@chelsio.com
Subject: Re: [dpdk-dev] [PATCH 0/2] net/cxgbe: minor fixes for link related changes
Date: Tue, 19 Jan 2021 01:52:16 +0000	[thread overview]
Message-ID: <076ff234-1bab-8075-b608-132204a34214@intel.com> (raw)
In-Reply-To: <cover.1610730372.git.rahul.lakkireddy@chelsio.com>

On 1/15/2021 5:19 PM, Rahul Lakkireddy wrote:
> Patch 1 fixes issue with link status always getting set to down by
> driver for every link config change request. This is not required
> for some link config changes, like Tx/Rx pause on/off. Instead,
> driver should rely on actual link status returned by firmware in
> link config change reply.
> Patch 2 fixes issue with link FEC retraining during probe. If
> firmware had already saved FEC before probe is completed, then
> use the saved FEC for further link configuration, instead of
> triggering link retraining. Also simplifies get fec ops.
> Thanks,
> Rahul
> Rahul Lakkireddy (2):
>    net/cxgbe: do not link down for every link config change
>    net/cxgbe: avoid link FEC retraining during probe
>   drivers/net/cxgbe/base/t4_hw.c   | 17 ++++++++++++-----
>   drivers/net/cxgbe/cxgbe_ethdev.c | 21 +++++----------------
>   2 files changed, 17 insertions(+), 21 deletions(-)

Set squashed into relevant commits in next-net, thanks.

      parent reply	other threads:[~2021-01-19  1:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15 17:19 Rahul Lakkireddy
2021-01-15 17:19 ` [dpdk-dev] [PATCH 1/2] net/cxgbe: do not link down for every link config change Rahul Lakkireddy
2021-01-15 17:19 ` [dpdk-dev] [PATCH 2/2] net/cxgbe: avoid link FEC retraining during probe Rahul Lakkireddy
2021-01-19  1:52 ` Ferruh Yigit [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=076ff234-1bab-8075-b608-132204a34214@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=kaara.satwik@chelsio.com \
    --cc=rahul.lakkireddy@chelsio.com \


* 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).