From: 贾学涛 <jiaxt@sinogrid.com>
To: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "letaotor@gmail.com" <letaotor@gmail.com>
Subject: Re: [dpdk-dev] [PATCH] ixgbe: fix LSC callback
Date: Tue, 1 Sep 2015 16:09:53 +0800 [thread overview]
Message-ID: <55E55D51.10201@sinogrid.com> (raw)
In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC0909D4282A@shsmsx102.ccr.corp.intel.com>
Hi Wenzhuo,
I bond 82599 ports with mode 802.3ad, the bonding port can't work
properly. But bonding with i350 ports works properly. I found the
registered callback function bond_ethdev_lsc_event_callback by
__eth_bond_slave_add_lock_free was not executed when link status
changed. I compared ixgbe driver with igb driver, ixgbe's LSC interrupt
action without _rte_eth_dev_callback_process.
On 09/01/2015 03:42 PM, Lu, Wenzhuo wrote:
> Hi Shelton,
>
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Shelton Chia
>> Sent: Tuesday, September 1, 2015 2:22 PM
>> To: dev@dpdk.org
>> Cc: letaotor@gmail.com
>> Subject: [dpdk-dev] [PATCH] ixgbe: fix LSC callback
>>
>> add _rte_eth_dev_callback_process to call callback func
> Would you like to give more details about why we need this patch? Thanks.
>> Signed-off-by: Shelton Chia <jiaxt@sinogrid.com>
>> ---
>> drivers/net/ixgbe/ixgbe_ethdev.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/net/ixgbe/ixgbe_ethdev.c b/drivers/net/ixgbe/ixgbe_ethdev.c
>> index b8ee1e9..4e4c118 100644
>> --- a/drivers/net/ixgbe/ixgbe_ethdev.c
>> +++ b/drivers/net/ixgbe/ixgbe_ethdev.c
>> @@ -2775,6 +2775,8 @@ ixgbe_dev_interrupt_action(struct rte_eth_dev *dev)
>>
>> ixgbe_dev_link_status_print(dev);
>>
>> + __rte_eth_dev_callback_process(dev,
>> RTE_ETH_EVENT_INTR_LSC);
>> +
>> intr_enable_delay = true;
>> }
>>
>> --
>> 2.5.0
--
贾学涛
信诺瑞得西安研发中心
next prev parent reply other threads:[~2015-09-01 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 6:21 Shelton Chia
2015-09-01 7:42 ` Lu, Wenzhuo
2015-09-01 8:09 ` 贾学涛 [this message]
2015-09-01 8:38 ` 贾学涛
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=55E55D51.10201@sinogrid.com \
--to=jiaxt@sinogrid.com \
--cc=dev@dpdk.org \
--cc=letaotor@gmail.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 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).