From: "Kinsella, Ray" <mdr@ashroe.eu>
To: Harman Kalra <hkalra@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/2] common/cnxk: send link event to VF
Date: Mon, 27 Sep 2021 14:06:16 +0100 [thread overview]
Message-ID: <12c6738b-339f-4a1d-853a-05bee4534d1f@ashroe.eu> (raw)
In-Reply-To: <20210730160829.13597-1-hkalra@marvell.com>
On 30/07/2021 17:08, Harman Kalra wrote:
> Currently link event is only sent to the PF by AF as soon as it comes
> up, or in case of any physical change in link. PF will broadcast
> these link events to all its VFs as soon as it receives it.
> But no event is sent when a new VF comes up, hence it will not have
> the link status.
> Adding support for sending link status to the VF once it comes up
> successfully.
>
> Signed-off-by: Harman Kalra <hkalra@marvell.com>
> ---
> drivers/common/cnxk/roc_dev.c | 33 ++++++++++++++++++++++++++++++
> drivers/common/cnxk/roc_dev_priv.h | 5 +++++
> drivers/common/cnxk/roc_nix.h | 7 +++++++
> drivers/common/cnxk/roc_nix_mac.c | 23 +++++++++++++++++++++
> drivers/common/cnxk/version.map | 2 ++
> 5 files changed, 70 insertions(+)
>
Acked-by: Ray Kinsella <mdr@ashroe.eu>
prev parent reply other threads:[~2021-09-27 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 16:08 Harman Kalra
2021-07-30 16:08 ` [dpdk-dev] [PATCH 2/2] net/cnxk: callback for getting link status Harman Kalra
2021-09-07 2:59 ` Jerin Jacob
2021-09-15 8:32 ` Nithin Kumar Dabilpuram
2021-09-16 14:31 ` [dpdk-dev] [PATCH 1/2] common/cnxk: send link event to VF Jerin Jacob
2021-09-27 13:06 ` Kinsella, Ray [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=12c6738b-339f-4a1d-853a-05bee4534d1f@ashroe.eu \
--to=mdr@ashroe.eu \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.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).