From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-fw-33001.amazon.com (smtp-fw-33001.amazon.com [207.171.189.228]) by dpdk.org (Postfix) with ESMTP id 1109758FE for ; Tue, 23 Sep 2014 20:47:53 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1411498443; x=1443034443; h=from:to:subject:date:message-id:mime-version; bh=kIsgYxHvIEOh1EemjD+6N9WISMkzPH9deJxcAN3MdgI=; b=Y/FIFn7U9bsfLffchJ/DgjVM13VkdtjclyyrMLd6c4XSn/JNpOam1H2C +/Orj4W19Fw+LHwv41xo7srSF5hnu2y7PHdMusCWihh8ls/LrSqv2gnHs ie6fDgSx5lSJqcUoK4ejUEPLRZUfErpPFeAj+uB/CEzAJnkGkMWQieT0N Y=; X-IronPort-AV: E=Sophos;i="5.04,581,1406592000"; d="scan'208,217";a="106139422" Received: from email-inbound-relay-62001.pdx2.amazon.com ([10.241.21.123]) by smtp-border-fw-out-33001.sea14.amazon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 23 Sep 2014 18:53:59 +0000 Received: from ex10-hub-9002.ant.amazon.com (pdx2-ws-svc-lb17-vlan2.amazon.com [10.247.140.66]) by email-inbound-relay-62001.pdx2.amazon.com (8.14.7/8.14.7) with ESMTP id s8NIrvro010655 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK) for ; Tue, 23 Sep 2014 18:53:59 GMT Received: from EX10-MBX-31007.ant.amazon.com ([fe80::dc2d:ebf:d4a1:fac]) by ex10-hub-9002.ant.amazon.com ([::1]) with mapi id 14.03.0181.006; Tue, 23 Sep 2014 11:53:57 -0700 From: "Wang, Shawn" To: "dev@dpdk.org" Thread-Topic: Can not init NIC after merge to DPDK 1.7 problem Thread-Index: Ac/XXW46B/qzlYm1RhequX4gunssXg== Date: Tue, 23 Sep 2014 18:53:57 +0000 Message-ID: <12C2AAD9525203489F7B523D670129D91CA7579B@ex10-mbx-31007.ant.amazon.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.17.1.118] MIME-Version: 1.0 Precedence: Bulk Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] Can not init NIC after merge to DPDK 1.7 problem X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2014 18:47:55 -0000 Hi: We are using our own Makefile in building dpdk program. Recently we are wor= king on upgrading from DPDK 1.3 to DPDK 1.7. I found the rte_ixgbe_pmd_init= has been replaced by PMD_REGISTER_DRIVER. So I delete rte_ixgbe_pmd_init c= alls. But after that, our dpdk program could not correctly find the NIC any= more. After digging into it a little more, I found the code dose not correc= tly register the driver type we are using, which is ixgbe. To isolate the problem, I hacked a smal example l3fwd, and only have the ma= in.c file like this for my testing purpose. #include #include #include "main.h" int MAIN(int argc, char **argv) { /* init EAL */ int ret =3D rte_eal_init(argc, argv); printf("ret %d\n", ret); return 0; } I found if I use the Makefile provided in the example, the program will fin= d the ixgbe NIC. But if I just use these 2 commands to compile and link it.= It will not find the ixgbe NIC. gcc -I../../x86_64-native-linuxapp-gcc/include -L../../x86_64-native-linuxa= pp-gcc/lib -lrte_eal -c main.c gcc -o l3fwd main.o -L../../x86_64-native-linuxapp-gcc/lib -lrte_eal -lrte_= distributor -lrte_pipeline -lrte_port -lrte_timer -lrte_hash -lrte_acl -lm = -lrt -lrte_mbuf -lethdev -lrte_malloc -lrte_mempool -lrte_ring -lc -lm -lrt= e_cmdline -lrte_cfgfile -lrte_pmd_bond -lrte_pmd_ixgbe -lrte_pmd_e1000 -lrt= e_pmd_ring -lpthread -ldl -lrt Can someone share some light on what is magic of the dpdk Makefile to corre= ctly register the NIC type? Thank you so much. Xingbo Wang