From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f176.google.com (mail-wr0-f176.google.com [209.85.128.176]) by dpdk.org (Postfix) with ESMTP id E94879159 for ; Thu, 25 May 2017 08:03:21 +0200 (CEST) Received: by mail-wr0-f176.google.com with SMTP id z52so66233863wrc.2 for ; Wed, 24 May 2017 23:03:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=weka.io; s=google; h=from:to:cc:subject:date:message-id:organization:in-reply-to :references:mime-version:content-transfer-encoding; bh=albUpuYORV9V/vN369ySaOjTMEQdEulcALzfy0wHPxY=; b=k6iDa6IFPRvD+SW2sHRDTsL+M48cQ2xKZHw3DeK1m2ONZjulwmmBtF/1cxIsWDV+SQ maGWVlR5H6dzFtwlsWajxADd8y98/k6EYq506Lve3AKRgp3Wdoe9TjO4G7cuh8r2WFD7 1k5SOaiZPfgNtA3YyH9TerMop+/0BNWp94Nxo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :in-reply-to:references:mime-version:content-transfer-encoding; bh=albUpuYORV9V/vN369ySaOjTMEQdEulcALzfy0wHPxY=; b=hefgPl9fNKOkq32kzL2tQi9CP57pwC2Io4zgPjSIdJrmqY8TKMPS8dhKCid3Q6aD1p ASjMldcZ0TnH0tHoZH70MB4/1TSp12K+vvIqcaLJE/mFNkxhWCTm1YAxK+ig2AXOoyJj eym8ES97QR/P4QSmgOqNdPvrkBhPlJlgSaIpXiX59bel5setwXwbinWajl97f7yHH2gY CAKsc4TZiKJrSpcrF72dRgBpnlHBXwxFhjQN3OBA1MK7nP5Abv3RX6CIMGxpsjjAkn6X UgsLFDmZeDwXRn6H5lpqH5hoBZ58C5IahbEA+oRVcyh0sA/6IpC8Q2dNm4wi6ZhM421q Wpzw== X-Gm-Message-State: AODbwcBhTgvoystsJkXZdsL7sewT4h2yNUZ4PgJmfzykKUkRuAr0rrGN jZ1dgXQ7SB3E9D9lFRw= X-Received: by 10.223.171.68 with SMTP id r4mr22592354wrc.67.1495692201176; Wed, 24 May 2017 23:03:21 -0700 (PDT) Received: from polaris.localnet (bzq-82-81-85-138.red.bezeqint.net. [82.81.85.138]) by smtp.gmail.com with ESMTPSA id s29sm7311839wrb.21.2017.05.24.23.03.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 May 2017 23:03:20 -0700 (PDT) From: Gregory Etelson To: "Lu, Wenzhuo" Cc: "dev@dpdk.org" , "users@dpdk.org" , "Yigit, Ferruh" Date: Thu, 25 May 2017 09:03:19 +0300 Message-ID: <149580724.I1KizxjscO@polaris> Organization: Weka.IO In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC09093B5BCB14@shsmsx102.ccr.corp.intel.com> References: <8509342.3MbcxIPMKs@polaris> <3497961.mUtAKJcRhq@polaris> <6A0DE07E22DDAD4C9103DF62FEBC09093B5BCB14@shsmsx102.ccr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] IXBGE VF: link state detection X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2017 06:03:22 -0000 Hello, In that case if I need reliable link state detection the only option is PF link verification. Is it so ? Thank you. Regards, Gregory On Thursday, 25 May 2017 08:44:56 IDT Lu, Wenzhuo wrote: Hi Gregory, Yes, I remember i40e kernel driver has the watchdog too. I guess maybe all = the NICs=E2=80=99 kernel driver has the similar mechanism. Not sure as I ha= ven=E2=80=99t checked J =20 =20 Best regards Wenzhuo Lu =20 *From:* Gregory Etelson [mailto:gregory@weka.io]=20 *Sent:* Thursday, May 25, 2017 1:22 PM *To:* Lu, Wenzhuo *Cc:* dev@dpdk.org; users@dpdk.org; Yigit, Ferruh *Subject:* Re: IXBGE VF: link state detection =20 Hello, What about i40e VF PMD ? Does it have reliable link state monitoring ? Thank you. Regards, Gregory On Thursday, 25 May 2017 08:01:00 IDT Lu, Wenzhuo wrote: Hi Gregory, The mechanism is different. Kernel driver has a watchdog to check the link = state periodically. So, it can reset the link automatically. =20 =20 Best regards Wenzhuo Lu =20 *From:* Gregory Etelson [mailto:gregory@weka.io[1]]=20 *Sent:* Thursday, May 25, 2017 11:45 AM *To:* Lu, Wenzhuo *Cc:* dev@dpdk.org[2]; users@dpdk.org[3]; Yigit, Ferruh *Subject:* Re: IXBGE VF: link state detection =20 Hello, In this case I would expect ixgbe VF bound to kernel driver also fail on link up detection In my tests, VFs bound to kernel drivers operate correctly. Regards, Gregory On Thursday, 25 May 2017 03:56:34 IDT Lu, Wenzhuo wrote: Hi Gregory, After you turned the port donw/up, PF will re-init the VF=E2=80=99s registe= rs. So, VF cannot work correctly. That=E2=80=99s why you can know link down= but not link up and have to reset the process. =20 =20 Best regards Wenzhuo Lu =20 *From:* Gregory Etelson [mailto:gregory@weka.io[1]]=20 *Sent:* Wednesday, May 24, 2017 5:50 PM *To:* dev@dpdk.org[2] *Cc:* users@dpdk.org[3]; Yigit, Ferruh; Lu, Wenzhuo *Subject:* IXBGE VF: link state detection =20 Hello, In my tests DPDK-17.05.0 process queries link state with rte_eth_link_get()= each 50 msec during 5-20 MB/sec IOs flow. I turn Ethernet switch port down and up and check IXGBE VF PMD reaction to = link state changes.=20 VF PMD correctly recognize link down events but may miss link up. When the fault occurs, subsequent calls to rte_eth_link_get will return lin= k_status =3D=3D 0 forever. I need to reset DPDK process to get correct link state value. My debugging shows that in case of the fault, mbx->ops.read(hw, &in_msg, 1,= 0) in ixgbe_check_mac_link_vf keeps returning non-zero value Regards, Gregory=20 =20 =20 =2D------- [1] mailto:gregory@weka.io [2] mailto:dev@dpdk.org [3] mailto:users@dpdk.org