[dpdk-dev] [PATCH v2] eal: change default per socket memory allocation

> 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), and dpdk is

[dpdk-dev] [PATCH v2] eal: change default per socket memory allocation

Hi Venky, There were comments on the first version of this patch and you suggested to try this new implementation. So do you acknowledge this patch? Thanks for your review 2014-05-09 15:30, David Marchand: > From: Didier Pallard > > Currently, if there is more memory in hugepages than the amo

[dpdk-dev] [PATCH v2] eal: change default per socket memory allocation

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 sock

[dpdk-dev] [PATCH v2] eal: change default per socket memory allocation

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