Hi Bhanuprakash, Thanks for the info. Helpful!
Regards Kapil. On Mon, Oct 3, 2016 at 5:41 PM, Bodireddy, Bhanuprakash < bhanuprakash.bodire...@intel.com> wrote: > > >-----Original Message----- > >From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Kapil > >Adhikesavalu > >Sent: Monday, October 3, 2016 12:07 PM > >To: dev@openvswitch.org; disc...@openvswitch.org > >Subject: [ovs-dev] Hugepages allocation > > > >Hi, > > > >1. in INSTALL.DPDK.md, huge page size is recommended as 2MB pages. > Earlier > >i remember seeing some reference to use 1GB huge pages. is there any > >noticeable performance improvement in using 1G hugepages vs 2M pages ? > > We did some benchmarks and found that there isn't any significant > performance difference using 2MB hugepages over 1GB pages. > > >2. is there a way to allocate 1G hugepages using sysctl. Default hugepage > size > >is 2M and i didn't find any way to modify it using sysctl. is grub config > the only > >way to allocate 1GB pages ? > > Yes, for this one has to build kernel with CONFIG_CMA. In case the kernel > is built with this, one can allocate hugepages at run time as below > echo N > /sys/devices/system/node/nodeX/hugepages/hugepages- > 1048576kB/nr_hugepages > > >3. Is there any difference in allocating huge pages run time vs > >persistent(/etc/sysctl.d/hugepages.conf) ? will the hugepages allocated > at > >runtime will be fragmented or something? > The only advantage of allocating hugepages at boot time is you are sure to > get the requested pages as the memory isn't fragmented. > if memory is too fragmented the chances are that fewer pages would be > allocated by kernel than requested. > > > > >Regards > >Kapil. > >_______________________________________________ > >dev mailing list > >dev@openvswitch.org > >http://openvswitch.org/mailman/listinfo/dev > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
