From: Simon Kuenzer
Enable users to specify the lcore id that is used as master lcore.
Signed-off-by: Simon Kuenzer
Signed-off-by: Thomas Monjalon
---
app/test/test.c| 1 +
app/test/test_eal_flags.c | 51 ++
lib/librte_
From: Patrick Lu
EAL -c option allows the user to enable any lcore in the system.
Often times, the user app wants to know 1st enabled core, 2nd
enabled core, etc, rather than phyical core ID (rte_lcore_id().)
The new API rte_lcore_index() will return an index from enabled lcores
starting from ze
From: Didier Pallard
New platforms have more than 64 cores.
Now that cores can be specified with a list, we are not limited anymore to 64.
Set default max cores number to 128.
Signed-off-by: Didier Pallard
Acked-by: David Marchand
---
config/common_bsdapp | 2 +-
config/common_linuxapp | 2
From: Didier Pallard
In current version, used cores can only be specified using a bitmask.
It will now be possible to specify cores in 2 different ways:
- Using a bitmask (-c [0x]nnn): bitmask must be in hex format
- Using a list in following format: -l [-c2][,c3[-c4],...]
The letter -l can stan
Some adjustments are done after options parsing and are common
to Linux and BSD.
Remove process_type adjustment in rte_config_init() because
it is already done in eal_parse_args().
eal_proc_type_detect() is kept duplicated because it open a
file descriptor which is used later in each eal.c.
Signe
No need to have duplicated check for common options.
Some flags are set for options -c and -m in order to simplify the
checks.
Signed-off-by: Thomas Monjalon
---
lib/librte_eal/bsdapp/eal/eal.c| 54 ++
lib/librte_eal/common/eal_common_options.c | 53 +
Now that internal config structure is common to Linux and BSD,
we can have a common function to initialize it.
Signed-off-by: Thomas Monjalon
---
lib/librte_eal/bsdapp/eal/eal.c| 24 +--
lib/librte_eal/common/eal_common_options.c | 37 ++
l
Some guards are missing or have a wrong name.
Others have LINUXAPP in their name but are now common.
Signed-off-by: Thomas Monjalon
---
lib/librte_eal/common/eal_filesystem.h | 6 +++---
lib/librte_eal/common/eal_hugepages.h| 6 +++---
lib/librte_eal/common/eal_internal_cfg.h | 4 ++--
lib
No need to have different headers for Linux and BSD.
These files are identicals with exception of internal config which has
uio and vfio fields only useful for Linux.
Signed-off-by: Thomas Monjalon
---
app/test/test_eal_fs.c | 2 +-
lib/librte_eal/bsdapp/eal/Makefil
The directory include/ should be reserved to public headers.
Signed-off-by: Thomas Monjalon
---
lib/librte_eal/bsdapp/eal/Makefile | 1 +
lib/librte_eal/common/{include => }/eal_options.h| 0
lib/librte_eal/common/{include => }/eal_private.h| 0
lib/librte_e
There are some pending patches which requires to factorize some EAL parts
in order to be correctly implemented.
This patchset do the required clean-up and rework these patches to improve
lcore handling:
Didier Pallard (2):
eal: add core list input format
config: support 128 cores
Patrick Lu (
On Sat, Nov 22, 2014 at 10:43:39PM +0100, Thomas Monjalon wrote:
> From: Didier Pallard
>
> In current version, used cores can only be specified using a bitmask.
> It will now be possible to specify cores in 2 different ways:
> - Using a bitmask (-c [0x]nnn): bitmask must be in hex format
> - Usi
Tim,
cc-ing Paolo and qemu-devel@ again in order to get their take on it.
>>> Did you make any progress in Qemu/KVM community?
>>> We need to be sync'ed up with them to be sure we share the same goal.
>>> I want also to avoid using a solution which doesn't fit with their plan.
>>> Remember that w
-Original Message-
From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Neil Horman
Sent: Friday, November 21, 2014 8:21 PM
To: O'driscoll, Tim
Cc: dev at dpdk.org
Subject: Re: [dpdk-dev] Next Community Call, Tuesday 2nd December, 8:00 AM GMT
On Fri, Nov 21, 2014 at 04:08:53PM +, O'd
14 matches
Mail list logo
