From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 49E6DDDC0 for ; Mon, 5 Jun 2023 19:05:06 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 79BB9C433EF; Mon, 5 Jun 2023 19:05:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1685991906; bh=7LVUVd0XvraoEN/YjTHAI4hPxvvrBvtSL1v2/CGmCys=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=fgKZSg7bIbcv1Leyrk4is08VMlfrCtnQvkobYEg3P+MskvJVvgytlW2cLaruuy5Lb MbwR1Z8ldgvC5CNkyD5MdowE5sdYTnG3ucPpQgSmgqUrlQ+7DL2BXDKTXWYowlvIsO VX2P1VwQo3D7gV7lw3Dv+6NUV+AMWC0sDJITl90fPJnoEV2G4Ww+gEMTv1rvm0Z3E5 PpDV6zrlLYG+yezyjNmxz596hRHk6zvhmG2b3DDEhCeuezIAiXD064kaxvzf6DfQOF EGByZz5DuQ2XvuPmVUPfk799u++2tOjYWsdhPY492Dy3sIVXoxHVnNo9SekPzMU7e+ sFj5Ai+JyYOBw== Date: Mon, 5 Jun 2023 12:05:05 -0700 From: Jakub Kicinski To: Shannon Nelson Cc: netdev@vger.kernel.org, davem@davemloft.net, brett.creeley@amd.com, drivers@pensando.io, Nitya Sunkad Subject: Re: [PATCH net-next] ionic: add support for ethtool extended stat link_down_count Message-ID: <20230605120505.71f518ae@kernel.org> In-Reply-To: References: <20230602173252.35711-1-shannon.nelson@amd.com> <20230602234708.03fbb00e@kernel.org> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Mon, 5 Jun 2023 09:26:25 -0700 Shannon Nelson wrote: > > Hm, could you say more about motivation? The ethtool stat is supposed to > > come from HW and represent PHY-level flap count. It's used primarily to > > find bad cables in a datacenter. Is this also the use case for ionic? > > It's unclear to me whether ionic interfaces are seeing an actual PHY or > > just some virtual link state of the IPU and in the latter case it's not > > really a match. > > This is a fair question - yes, it is possible that the FW could fake it, > but normally this is a signal from the HW. However, I suppose it would > be best to only have the PF reporting this counter, and not the VFs, > which is currently the case here. I'll have Nitya modify this for PF only. Perfect, thanks!