From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-f44.google.com (mail-wm1-f44.google.com [209.85.128.44]) by dpdk.org (Postfix) with ESMTP id 3F85D5B20 for ; Fri, 26 Oct 2018 13:27:20 +0200 (CEST) Received: by mail-wm1-f44.google.com with SMTP id y144-v6so1085732wmd.4 for ; Fri, 26 Oct 2018 04:27:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=GfQQb0RXty1Ilaxf2FG38e0pZOf/zy//XFUsFSLOtRE=; b=D9moawpNYmtGte0HLZ20zSFOEMY47/ywrqcf52Tbw2/L4hVARy2B2vU+Vh8Ffd6ZKL 3OyKPuJd1WOqqFB2qqC7WGjM9f5LVG9WcLsFBThaWzm4QFhtOn5BUWiterKOFrKMKJdx 0MNpGPXa5rFHN/SILIrdvFQ05EouFs3vrB612pAzm29Y60EKO7hiKV6175YY5NaKsity V7P8jOWF+wEqlF1bckjw36uYat8I+PmLDFwCm4oFuYBFQIh85f9mGjkoSus2REVCMryn b0KW1Q2K3QDMDBqWOT7c9v3XQq53T34BJapg+gbZCr+6nMO9Jdwe1ojl38VNSh7hfN59 Xrig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=GfQQb0RXty1Ilaxf2FG38e0pZOf/zy//XFUsFSLOtRE=; b=BIIBPig+M7SQNbdTgM/ui4DODA2gz8PoRQvLQLF+fAUJ3vVs3taT+gVZA/TaAeZZvs 8942Xuw2Pm4aBhekXHDqmrbRbZ2DjXWUgCJUqVc1T00Byd0Fcull8uzju6SuimkohmkS VG7rpLHl5EHDfnsVVgKOrvyEUmTO9xk+/5p69ugnNUMpPm6ee7tWTcQ+GA6ZQUzaFKVA 8Ja9GeXAJ1kDVdJpHF+GLLF35W2034jpEbCiTw+IZ065I8FKsN0Ls76uOUUHaQ3OsavU DW0TPdq4W1TOixmIT5HMk1GP3WOrM53/vaYjE30V0XEkM9+F5nCY8454U0LKZYLKLLrw iHBQ== X-Gm-Message-State: AGRZ1gIzvWwc5VJwDHMvNZ67nZlTdQfdfziE6qc6+z1hfQ2Ohmm5hhA+ Z0PYCMWLaIT7L1mDKho6QyQ5Bg== X-Google-Smtp-Source: AJdET5fXRobyRr7Hi5UZLGMqvuaeSd5X+xCSfo70MAwjumAwS6CTVtV4l3SgwHgo3vu9GallEWbUUg== X-Received: by 2002:a1c:9d86:: with SMTP id g128-v6mr5423812wme.67.1540553239366; Fri, 26 Oct 2018 04:27:19 -0700 (PDT) Received: from bidouze.vm.6wind.com (host.78.145.23.62.rev.coltfrance.com. [62.23.145.78]) by smtp.gmail.com with ESMTPSA id l70-v6sm9046718wma.0.2018.10.26.04.27.18 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 26 Oct 2018 04:27:18 -0700 (PDT) Date: Fri, 26 Oct 2018 13:26:59 +0200 From: =?iso-8859-1?Q?Ga=EBtan?= Rivet To: Paul T Cc: "users@dpdk.org" Message-ID: <20181026112659.ffiuhys7vcwu7x27@bidouze.vm.6wind.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) Subject: Re: [dpdk-users] Query SFP+ module information 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: Fri, 26 Oct 2018 11:27:20 -0000 Hi Paul, On Fri, Oct 26, 2018 at 10:24:35AM +0000, Paul T wrote: > Hi, > > Is it possible to query information about the SFP+ modules inserted into a X710 10GbE network card via DPDK? > > I have a specific user case where its a possibility that a 25GbE SFP+ module could be inserted into a 10GbE X710. The error that is thrown when this happens is: > > PMD: eth_i40e_dev_init(): Failed to sync phy type: -95 > EAL: Error - exiting with code: 1 > Cause: Requested device 0000:66:00.0 cannot be used > > I'm wondering if there is a way to query the module before this stage so there is a more graceful way to handling the unusable module. Unfortunately, no. It is possible to query the module once the port is initialized, there are two functions for that. However the port needs to be initialized already. Additionally, some adapters might power off the module completely on link down, in which case module info would not be available. But your specific use-case does not seem feasible. -- Gaëtan Rivet 6WIND