From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cos-us-iron02k.cos.keysight.com (cos-us-iron02k.cos.keysight.com [192.25.5.36]) by dpdk.org (Postfix) with ESMTP id AB3362A5D for ; Mon, 25 Apr 2016 13:49:55 +0200 (CEST) X-IPAS-Result: A2C0AwCPAx5XcxQYjJxegmyBH4EDu3OGDgKBYhEBAQEBAQEBEgEXMy+EQwUtXgEqViYBBBuIIqAfoD8MHo8rTIJfgisFmA+dJY8vNoQXiFMBfgEBAQ X-IronPort-AV: E=Sophos;i="5.24,532,1455001200"; d="scan'208,217";a="29852005" Received: from wcosexch01k.cos.is.keysight.com (HELO 2k10hubs.keysight.com) ([156.140.24.20]) by cos-us-iron02k.cos.keysight.com with ESMTP/TLS/AES128-SHA; 25 Apr 2016 05:39:00 -0600 Received: from wcosexch02k.cos.is.keysight.com ([169.254.2.20]) by wcosexch01k.cos.is.keysight.com ([169.254.3.42]) with mapi id 14.03.0266.001; Mon, 25 Apr 2016 05:49:53 -0600 From: To: Thread-Topic: Link Status and Interrupts in 2.2.0 Thread-Index: AdGe6FEPopc4Nd0+S1GKBxnuvLUDww== Date: Mon, 25 Apr 2016 11:49:52 +0000 Message-ID: <22C95CA62CBADB498D32A348F0F073BC116CC81F@wcosexch02k.cos.is.keysight.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [156.140.13.71] x-tm-as-product-ver: SMEX-11.0.0.4255-8.000.1202-22282.006 x-tm-as-result: No--53.647700-8.000000-31 x-tm-as-user-approved-sender: No x-tm-as-user-blocked-sender: No MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] Link Status and Interrupts in 2.2.0 X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2016 11:49:56 -0000 Hello All, Been adding in support for the interrupt handler for the link status for po= rts on an X710 card. Before I changed the lsc field of the intr_conf to 1, I was able to see the= link status information correctly. The documentation does say that if interrupts are enabled, the rte_eth_link= _get function recovers the information from a structure that the interrupt = host thread fills in, rather than going to the card it's self. This seems reasonable, however....once you've had an interrupt then all is = good, But if the link was "active" when dpdk and my app starts up, then no interr= upt is generated, which then means that global structure is not filled in, = so I see get link status status is 0 speed is 0 duplex is 0 if I turn the lasers on and off on my source I get the expected values, sin= ce the interrupt event causes the global data to be populated. get link status status is 1 speed is 10000 duplex is 2 So the question is, how do I use the LSC interrupts via the "rte_eth_dev_ca= llback_register" function, but get the correct values in the link status information if no interrupts = occur? I saw a submission to the patchwork 7160, dated Sep 24 2015 but it was mark= ed as not applicable , archived..... Many Thanks Martin R&D Engineer Keysight Technologies UK Ltd