From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-f42.google.com (mail-wg0-f42.google.com [74.125.82.42]) by dpdk.org (Postfix) with ESMTP id C6A357FB8 for ; Mon, 24 Nov 2014 16:08:09 +0100 (CET) Received: by mail-wg0-f42.google.com with SMTP id z12so12497865wgg.1 for ; Mon, 24 Nov 2014 07:18:58 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=Hrj2l5LcSrPPWoxeZqYk6DbItNpwjg5JU6b68pIvOrc=; b=MZgk++MBK8sHJ+uk4tskv+Z3XYsCcQKBWWDARke61v3HhwebUAzFubrYhNQ3LOTGFL uH+WTsCMZ2EtcE76Ns+KC0dqAe78Hd5pRGk94kl9qqqAKYZjuioaOxSNHVVDiOv24rzO nWJ0k4ztsfFIXNg+3jKjOzecN4l8P/YJZ/xfzMQLMb3j7lQNOgPtqaaAx8FE2qh7GMzF DB6OotPV4VPA/GkT9EO56zPdEPjDy4wIdBcdc3d2qEMnEWDOx48g9CDB9rrXOFkaWw2m qE0pl1ekd8jlD8MVZEYAHSZJbvLtq5JH6/y9G+hDnl/rxPL/9s5TVt+ejhJyEuexXbkF wPbQ== X-Gm-Message-State: ALoCoQlUHOPcF6MZfUf5r91PczTn8l+3qAryQyf28rCN6+qPEMYiH1hBYHXwlCulZPaWhCExs0Lp X-Received: by 10.194.177.225 with SMTP id ct1mr611750wjc.75.1416842338022; Mon, 24 Nov 2014 07:18:58 -0800 (PST) Received: from alcyon.dev.6wind.com (guy78-3-82-239-227-177.fbx.proxad.net. [82.239.227.177]) by mx.google.com with ESMTPSA id mw7sm12449043wib.14.2014.11.24.07.18.56 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 24 Nov 2014 07:18:57 -0800 (PST) From: David Marchand To: chaozhu@linux.vnet.ibm.com Date: Mon, 24 Nov 2014 16:18:51 +0100 Message-Id: <1416842331-7716-1-git-send-email-david.marchand@6wind.com> X-Mailer: git-send-email 1.7.10.4 In-Reply-To: References: Cc: dev@dpdk.org Subject: [dpdk-dev] [PATCH] eal: fix remaining checks for other 64bits architectures X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Nov 2014 15:08:10 -0000 RTE_ARCH_X86_64 can not be used as a way to determine if we are building for 64bits cpus. Instead, RTE_ARCH_64 should be used. Signed-off-by: David Marchand --- lib/librte_eal/linuxapp/eal/eal.c | 2 +- lib/librte_eal/linuxapp/eal/eal_hugepage_info.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/librte_eal/linuxapp/eal/eal.c b/lib/librte_eal/linuxapp/eal/eal.c index f9517c7..e321524 100644 --- a/lib/librte_eal/linuxapp/eal/eal.c +++ b/lib/librte_eal/linuxapp/eal/eal.c @@ -450,7 +450,7 @@ eal_parse_base_virtaddr(const char *arg) return -1; /* make sure we don't exceed 32-bit boundary on 32-bit target */ -#ifndef RTE_ARCH_X86_64 +#ifndef RTE_ARCH_64 if (addr >= UINTPTR_MAX) return -1; #endif diff --git a/lib/librte_eal/linuxapp/eal/eal_hugepage_info.c b/lib/librte_eal/linuxapp/eal/eal_hugepage_info.c index 73d1cdb..590cb56 100644 --- a/lib/librte_eal/linuxapp/eal/eal_hugepage_info.c +++ b/lib/librte_eal/linuxapp/eal/eal_hugepage_info.c @@ -324,7 +324,7 @@ eal_hugepage_info_init(void) * later they will be sorted */ hpi->num_pages[0] = get_num_hugepages(dirent->d_name); -#ifndef RTE_ARCH_X86_64 +#ifndef RTE_ARCH_64 /* for 32-bit systems, limit number of hugepages to 1GB per page size */ hpi->num_pages[0] = RTE_MIN(hpi->num_pages[0], RTE_PGSIZE_1G / hpi->hugepage_sz); -- 1.7.10.4