From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Leyi Rong <leyi.rong@intel.com>
Cc: wenzhuo.lu@intel.com, qi.z.zhang@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/ice: invoke callback func when link status change
Date: Wed, 16 Oct 2019 13:41:00 +0800 [thread overview]
Message-ID: <20191016054100.GL3725@intel.com> (raw)
In-Reply-To: <20191014084128.11791-1-leyi.rong@intel.com>
Hi, Leyi
On 10/14, Leyi Rong wrote:
>Call _rte_eth_dev_callback_process when link status change.
Could you elaborate more in commit log, like why we need this patch, what's the
impact without this patch, is it a fix, etc?
Thanks,
Xiaolong
>
>Signed-off-by: Leyi Rong <leyi.rong@intel.com>
>---
> drivers/net/ice/ice_ethdev.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
>diff --git a/drivers/net/ice/ice_ethdev.c b/drivers/net/ice/ice_ethdev.c
>index dfccef65d..ddcb4848b 100644
>--- a/drivers/net/ice/ice_ethdev.c
>+++ b/drivers/net/ice/ice_ethdev.c
>@@ -1293,6 +1293,7 @@ ice_interrupt_handler(void *param)
> uint8_t pf_num;
> uint8_t event;
> uint16_t queue;
>+ int ret;
> #ifdef ICE_LSE_SPT
> uint32_t int_fw_ctl;
> #endif
>@@ -1320,7 +1321,10 @@ ice_interrupt_handler(void *param)
> #else
> if (oicr & PFINT_OICR_LINK_STAT_CHANGE_M) {
> PMD_DRV_LOG(INFO, "OICR: link state change event");
>- ice_link_update(dev, 0);
>+ ret = ice_link_update(dev, 0);
>+ if (!ret)
>+ _rte_eth_dev_callback_process
>+ (dev, RTE_ETH_EVENT_INTR_LSC, NULL);
> }
> #endif
>
>--
>2.17.1
>
next prev parent reply other threads:[~2019-10-16 5:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 8:41 [dpdk-dev] [PATCH] net/ice: invoke callback func when link status change Leyi Rong
2019-10-16 5:41 ` Ye Xiaolong [this message]
2019-10-16 6:24 ` [dpdk-dev] [PATCH v2] " Leyi Rong
2019-10-16 6:41 ` Ye Xiaolong
2019-10-16 7:08 ` Rong, Leyi
2019-10-17 3:16 ` Ye Xiaolong
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=20191016054100.GL3725@intel.com \
--to=xiaolong.ye@intel.com \
--cc=dev@dpdk.org \
--cc=leyi.rong@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=wenzhuo.lu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.