> -----Original Message----- > From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Kevin > Traynor > Sent: Monday, December 7, 2015 5:58 PM > To: dev@openvswitch.org > Subject: [ovs-dev] [PATCH] INSTALL.DPDK.md: Clarify DPDK arguments. > > Add some information about the DPDK -c and -n parameters. > > Signed-off-by: Kevin Traynor <kevin.tray...@intel.com> > Reported-by: Zoltan Kiss <zoltan.k...@linaro.org> > --- > INSTALL.DPDK.md | 14 ++++++++++++-- > 1 files changed, 12 insertions(+), 2 deletions(-) > > diff --git a/INSTALL.DPDK.md b/INSTALL.DPDK.md index 96b686c..ee016da > 100644 > --- a/INSTALL.DPDK.md > +++ b/INSTALL.DPDK.md > @@ -145,8 +145,18 @@ Using the DPDK with ovs-vswitchd: > > DPDK configuration arguments can be passed to vswitchd via `--dpdk` > argument. This needs to be first argument passed to vswitchd process. > - dpdk arg -c is ignored by ovs-dpdk, but it is a required parameter > - for dpdk initialization. > + The DPDK configuration arguments are passed to DPDK during DPDK > + initialization. > + > + The DPDK -c coremask is a required argument. To avoid wasted resources > + only one core should be set. The standard OVS threads (e.g. main > + process, handler, revalidator) will run on the core that is specified.
Might be worth mentioning that then there is a corresponding potential decrease in performance of revalidation and flow handling. > + > + Note: Ideally the -c coremask should not overlap with any pmd-cpu-mask > + setting where the DPDK polling threads will run to avoid cpu contention. > + > + The DPDK -n argument is a required argument that is a DPDK optimization > + for the number of memory channels. It is typically set to 4. > > ``` > export DB_SOCK=/usr/local/var/run/openvswitch/db.sock > -- > 1.7.4.1 > > _______________________________________________ > dev mailing list > dev@openvswitch.org > http://openvswitch.org/mailman/listinfo/dev _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
