From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id AD5A9A0559; Fri, 3 Jun 2022 10:59:59 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5531F40694; Fri, 3 Jun 2022 10:59:59 +0200 (CEST) Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by mails.dpdk.org (Postfix) with ESMTP id 611BC40691 for ; Fri, 3 Jun 2022 10:59:57 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1654246797; x=1685782797; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=F12FmM1l7+jD+rPMBIUTg62ZT6VplgcYRt1t+FyoEhQ=; b=iuxkzgkg61ECvoT9Qrvg33bLXkKCqevJI8cNUHeU3hzVNP76S5RsgznW s/R7UQoormYVSg/iu4R+u5Hyw0U3WmQ5WZVsP/fJx8ekJzUFlCtvz6pqa 4RzF8LFfcZQa3p8pRXE3abiLcElx97OfjAbypwTn3jH6+/QtZ1+93Uh1z l2BvPrBLeCeLGn4O2I0hdlOpWvKidbYOON/jKWv5EDWaoqGXwImTNKiRM XZ6+Bt4gOtBPyTQCBVSAIYXDLypEkQOHjkvhIsUuLPCzmb7AKDnY3A5Lx iCoK0b+7wt9OsEzuCqllcLcZMatNgUiN9kfeASvpRsEz1QN3EESUtLaDv w==; X-IronPort-AV: E=McAfee;i="6400,9594,10366"; a="258279722" X-IronPort-AV: E=Sophos;i="5.91,274,1647327600"; d="scan'208";a="258279722" Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Jun 2022 01:59:53 -0700 X-IronPort-AV: E=Sophos;i="5.91,274,1647327600"; d="scan'208";a="577940373" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.6.223]) by orsmga007-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 03 Jun 2022 01:59:52 -0700 Date: Fri, 3 Jun 2022 09:59:49 +0100 From: Bruce Richardson To: Mohan Gyara Cc: "dev@dpdk.org" , qiming.yang@intel.com, wenjun1.wu@intel.com Subject: Re: ixgbevf in dpdk doesn't seems to work (dpdk-stable-19.11.5) Message-ID: References: <1455096021.5344065.1654244040257.ref@mail.yahoo.com> <1455096021.5344065.1654244040257@mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1455096021.5344065.1654244040257@mail.yahoo.com> X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org + ixgbe maintainers on CC On Fri, Jun 03, 2022 at 08:14:00AM +0000, Mohan Gyara wrote: > Hi Team, > In our application we use 2 interfaces one to communicate towards gNB > and another to communicate with higher layers in a UE simulator NR > stack. Now we use a PCI whose driver is i40e and is bind to dpdk > vfio-pci driver and this works perfectly towards higher layer, but the > other interface PCI whose is ixgbe driver is bind to vfio-pci dpdk > driver and has some issues. > The issues are: > 1. Application crashes when "rte_eth_dev_mac_addr_add" function is > called when return with -1. > "on a 82599 VF, adding again the same MAC addr is not an idempotent > operation..." this is a comment, but the function ixgbevf_add_mac_addr > return -1 when memcmp(hw->mac.perm_addr, mac_addr) == 0) is true. > But above I commented the "return -1" and just returned from it, so > crash is not seen. > 2. After above 1, application is started successfully but then I do not > see any messages coming on this interface. This is the problem? > Could you guide me what is the issue? I see only issue with ixgbvf but > not for i40evf. > I am using dpdk-stable-19.11.5 version. > Kindly help me here. > Regards, > Mohan