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 3B2A0298F for ; Tue, 26 Apr 2016 08:03:14 +0200 (CEST) X-IPAS-Result: A2ArBABSBB9XcxYYjJxeHAGEcboDgXSGDgKBbxIBAQEBAQEBEgEXMy+EQQEBAQECATpPAgEIIhQQMiUBAQQbiBoIwy0BAQgBAQEBHIpshD9Mgl+CKwWTH4Rxj2iNQI8wJwyEGohtAX4BAQE X-IronPort-AV: E=Sophos;i="5.24,535,1455001200"; d="scan'208";a="29904418" Received: from wcosexch03k.cos.is.keysight.com (HELO 2k10hubs.keysight.com) ([156.140.24.22]) by cos-us-iron02k.cos.keysight.com with ESMTP/TLS/AES128-SHA; 25 Apr 2016 23:52:03 -0600 Received: from wcosexch02k.cos.is.keysight.com ([169.254.2.20]) by wcosexch03k.cos.is.keysight.com ([169.254.1.80]) with mapi id 14.03.0266.001; Tue, 26 Apr 2016 00:03:01 -0600 From: To: Thread-Topic: Link Status and Interrupts in 2.2.0 Thread-Index: AdGe6FEPopc4Nd0+S1GKBxnuvLUDwwAmITOg Date: Tue, 26 Apr 2016 06:03:01 +0000 Message-ID: <22C95CA62CBADB498D32A348F0F073BC116CC91D@wcosexch02k.cos.is.keysight.com> References: <22C95CA62CBADB498D32A348F0F073BC116CC81F@wcosexch02k.cos.is.keysight.com> In-Reply-To: <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-22284.005 x-tm-as-result: No--37.532000-8.000000-31 x-tm-as-user-approved-sender: No x-tm-as-user-blocked-sender: No Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [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: Tue, 26 Apr 2016 06:03:14 -0000 > Your application needs to make one call to check for current link state = after device is started. After that all updates can be done from the LSC in= terrupt callback. I made a call from the application, it just keeps getting 0s? If I change the lsc value to 0, then the call gets the correct value, since= it's asking the card, not the global value the callback fills in=20 I seem to be able to register a handler for the interrupt which gets called= , even if lsc is 0? Then I can call that once at startup, then use the callback???? Seems a little strange? Thanks for your help Stephen H. Martin Curran-Gray