dev at dpdk.org>
Subject: Re: [dpdk-dev] [PATCH RFC] eal: change default per socket memory
allocation
Sorry for spamming, but now that I think of it, I don't believe this change
makes much sense. If the user wants memory on specific sockets, there's already
--socket-mem option. If th
2014-05-06 10:05, Burakov, Anatoly:
> David Marchand:
> > Actually, if we don't care where memory is allocated, we can at least try
> > to have the more common setup work properly (i.e. spread memory
> > allocations based on used cores).
> > I can see no usual setup where you
> > want to use cores
Hi Thomas,
> Having --socket-mem option to explicitly configure NUMA is OK.
> Having -m option for simple configuration is OK.
Exactly. No explicit requirements - use -m option. Explicit socket requirements
- use --socket-mem option.
> So I don't understand why we shouldn't do this enhancement.
Hi David,
> Actually, if we don't care where memory is allocated, we can at least try to
> have the more common setup work properly (i.e. spread memory allocations
> based on used cores).
> I can see no usual setup where you want to use cores on a socket while having
> all memory on another soc
what is needed.
>
> -Venky
>
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Burakov, Anatoly
> Sent: Friday, May 02, 2014 1:54 AM
> To: Burakov, Anatoly; David Marchand; dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH RFC] eal: change
: Friday, May 02, 2014 1:54 AM
To: Burakov, Anatoly; David Marchand; dev at dpdk.org
Subject: Re: [dpdk-dev] [PATCH RFC] eal: change default per socket memory
allocation
Hi again David/Didier,
> Can I suggest to do an RTE_MAX between (internal_config.memory -
> total_mem) and (internal_config.
Hi again David/Didier,
> Can I suggest to do an RTE_MAX between (internal_config.memory -
> total_mem) and (internal_config.memory * cpu_per_socket[socket_id] +
> rte_lcore_count() - 1) / rte_lcore_count() ? I don't think it's a good idea
> to go
> over the requested amount. Let the last core hav
Hi David, Didier,
> + /* Set memory amount per socket; round up to be sure that
> sum of all */
> + /* sockets allocation is greater than requested memory size
> */
> + for (socket_id=0 ; socket_id socket_id++) {
> + internal_config.socket_me
From: Didier Pallard
Currently, if there is more memory in hugepages than the amount
requested by dpdk application, the memory is allocated by taking as much
memory as possible from each socket, starting from first one.
For example if a system is configured with 8 GB in 2 sockets (4 GB per
socket
9 matches
Mail list logo
