From: Shahaf Shuler <shahafs@mellanox.com>
To: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>,
"Yongseok Koh" <yskoh@mellanox.com>
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v2] net/mlx5: fix handling link status change event
Date: Thu, 18 Jan 2018 13:29:44 +0000 [thread overview]
Message-ID: <VI1PR05MB314906F2E7DAACB79B2B7E21C3E80@VI1PR05MB3149.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20180118075303.m2wvfkkcioypxj5w@shalom>
Thursday, January 18, 2018 9:53 AM, Nélio Laranjeiro
> On Wed, Jan 17, 2018 at 09:44:13AM -0800, Yongseok Koh wrote:
> > Even though link of a port gets down, device still can receive traffic.
> > That is the reason why mlx5_set_link_up/down() switches
> rx/tx_pkt_burst().
> > However, if link gets down by an external command (e.g. ifconfig), it
> > isn't effective. It is better to change burst functions when link
> > status change is detected.
> >
> > Fixes: 62072098b54e ("mlx5: support setting link up or down")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Yongseok Koh <yskoh@mellanox.com>
> Acked-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
>
> Thanks,
Applied to next-net-mlx, thanks.
>
> --
> Nélio Laranjeiro
> 6WIND
prev parent reply other threads:[~2018-01-18 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 23:48 [dpdk-dev] [PATCH] " Yongseok Koh
2018-01-16 8:20 ` Nélio Laranjeiro
2018-01-17 17:44 ` [dpdk-dev] [PATCH v2] " Yongseok Koh
2018-01-18 7:53 ` Nélio Laranjeiro
2018-01-18 13:29 ` Shahaf Shuler [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:
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=VI1PR05MB314906F2E7DAACB79B2B7E21C3E80@VI1PR05MB3149.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.com \
--cc=stable@dpdk.org \
--cc=yskoh@mellanox.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).