DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: konstantin.ananyev@intel.com, bruce.richardson@intel.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 1/2] config: remove obsolete machine descriptions
Date: Fri,  5 Feb 2016 23:00:37 +0100	[thread overview]
Message-ID: <1454709638-26357-2-git-send-email-thomas.monjalon@6wind.com> (raw)
In-Reply-To: <1454709638-26357-1-git-send-email-thomas.monjalon@6wind.com>

More and more machines and architectures are added without keeping
the lists up-to-date.
Replace the lists with a pointer to the reference directory.
The same kind of pointer is used for the supported compilers and environments.

Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
---
 config/common_bsdapp          | 19 ++++---------------
 config/common_linuxapp        | 19 ++++---------------
 mk/target/generic/rte.vars.mk |  8 --------
 3 files changed, 8 insertions(+), 38 deletions(-)

diff --git a/config/common_bsdapp b/config/common_bsdapp
index ed7c31c..50b9829 100644
--- a/config/common_bsdapp
+++ b/config/common_bsdapp
@@ -32,38 +32,27 @@
 
 #
 # define executive environment
-#
-# CONFIG_RTE_EXEC_ENV can be linuxapp, bsdapp
+# RTE_EXEC_ENV values are the directories in mk/exec-env/
 #
 CONFIG_RTE_EXEC_ENV="bsdapp"
 CONFIG_RTE_EXEC_ENV_BSDAPP=y
 
 ##
 ## machine can define specific variables or action for a specific board
-## RTE_MACHINE can be:
-## default  nothing specific
-## native   current machine
-## atm      Intel® Atom™ microarchitecture
-## nhm      Intel® microarchitecture code name Nehalem
-## wsm      Intel® microarchitecture code name Westmere
-## snb      Intel® microarchitecture code name Sandy Bridge
-## ivb      Intel® microarchitecture code name Ivy Bridge
-##
-## Note: if your compiler does not support the relevant -march options,
-## it will be compiled with whatever latest processor the compiler supports!
+## RTE_MACHINE values are the directories in mk/machine/
 ##
 #CONFIG_RTE_MACHINE="native"
 #
 ##
 ## define the architecture we compile for.
-## CONFIG_RTE_ARCH can be i686, x86_64, x86_64_32
+## RTE_ARCH values are the directories in mk/arch/
 ##
 #CONFIG_RTE_ARCH="x86_64"
 #CONFIG_RTE_ARCH_X86_64=y
 #
 ##
 ## The compiler we use.
-## Can be gcc, icc or clang.
+## RTE_TOOLCHAIN values are the directories in mk/toolchain/
 ##
 #CONFIG_RTE_TOOLCHAIN="gcc"
 #CONFIG_RTE_TOOLCHAIN_GCC=y
diff --git a/config/common_linuxapp b/config/common_linuxapp
index 74bc515..4866b96 100644
--- a/config/common_linuxapp
+++ b/config/common_linuxapp
@@ -32,38 +32,27 @@
 
 #
 # define executive environment
-#
-# CONFIG_RTE_EXEC_ENV can be linuxapp, bsdapp
+# RTE_EXEC_ENV values are the directories in mk/exec-env/
 #
 CONFIG_RTE_EXEC_ENV="linuxapp"
 CONFIG_RTE_EXEC_ENV_LINUXAPP=y
 
 ##
 ## machine can define specific variables or action for a specific board
-## RTE_MACHINE can be:
-## default  nothing specific
-## native   current machine
-## atm      Intel® Atom™ microarchitecture
-## nhm      Intel® microarchitecture code name Nehalem
-## wsm      Intel® microarchitecture code name Westmere
-## snb      Intel® microarchitecture code name Sandy Bridge
-## ivb      Intel® microarchitecture code name Ivy Bridge
-##
-## Note: if your compiler does not support the relevant -march options,
-## it will be compiled with whatever latest processor the compiler supports!
+## RTE_MACHINE values are the directories in mk/machine/
 ##
 #CONFIG_RTE_MACHINE="native"
 #
 ##
 ## define the architecture we compile for.
-## CONFIG_RTE_ARCH can be i686, x86_64, x86_64_32
+## RTE_ARCH values are the directories in mk/arch/
 ##
 #CONFIG_RTE_ARCH="x86_64"
 #CONFIG_RTE_ARCH_X86_64=y
 #
 ##
 ## The compiler we use.
-## Can be gcc, icc or clang.
+## RTE_TOOLCHAIN values are the directories in mk/toolchain/
 ##
 #CONFIG_RTE_TOOLCHAIN="gcc"
 #CONFIG_RTE_TOOLCHAIN_GCC=y
diff --git a/mk/target/generic/rte.vars.mk b/mk/target/generic/rte.vars.mk
index 53650c3..75a616a 100644
--- a/mk/target/generic/rte.vars.mk
+++ b/mk/target/generic/rte.vars.mk
@@ -50,8 +50,6 @@
 #   - can define CPU_ASFLAGS variable (overriden by cmdline value) that
 #     overrides the one defined in arch.
 #
-# examples for RTE_MACHINE: default, pc, bensley, tylesburg, ...
-#
 include $(RTE_SDK)/mk/machine/$(RTE_MACHINE)/rte.vars.mk
 
 #
@@ -69,8 +67,6 @@ include $(RTE_SDK)/mk/machine/$(RTE_MACHINE)/rte.vars.mk
 #     define in machine .mk)
 #   - may override any previously defined variable
 #
-# examples for RTE_ARCH: i686, x86_64
-#
 include $(RTE_SDK)/mk/arch/$(RTE_ARCH)/rte.vars.mk
 
 #
@@ -82,8 +78,6 @@ include $(RTE_SDK)/mk/arch/$(RTE_ARCH)/rte.vars.mk
 #   - define TOOLCHAIN_ASFLAGS variable (overriden by cmdline value)
 #   - may override any previously defined variable
 #
-# examples for RTE_TOOLCHAIN: gcc, icc
-#
 include $(RTE_SDK)/mk/toolchain/$(RTE_TOOLCHAIN)/rte.vars.mk
 
 #
@@ -94,8 +88,6 @@ include $(RTE_SDK)/mk/toolchain/$(RTE_TOOLCHAIN)/rte.vars.mk
 #   - define EXECENV_ASFLAGS variable (overriden by cmdline)
 #   - may override any previously defined variable
 #
-# examples for RTE_EXEC_ENV: linuxapp, bsdapp
-#
 include $(RTE_SDK)/mk/exec-env/$(RTE_EXEC_ENV)/rte.vars.mk
 
 # Don't set CFLAGS/LDFLAGS flags for kernel module, all flags are
-- 
2.7.0

  reply	other threads:[~2016-02-05 22:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05 22:00 [dpdk-dev] [PATCH 0/2] clean-up arch config Thomas Monjalon
2016-02-05 22:00 ` Thomas Monjalon [this message]
2016-02-05 22:00 ` [dpdk-dev] [PATCH 2/2] config: add a common x86 flag Thomas Monjalon
2016-02-11 11:34 ` [dpdk-dev] [PATCH 0/2] clean-up arch config Ananyev, Konstantin
2016-02-11 11:49   ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1454709638-26357-2-git-send-email-thomas.monjalon@6wind.com \
    --to=thomas.monjalon@6wind.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).