On Wed, Nov 01, 2017 at 05:46:43PM +0000, Sugesh Chandran wrote: > DPDK allocate memory regions at the time of vswitchd init. To run multiple > primary instance of DPDK including OVS on a single platform, the memory map > regions in the filesystem should be distinct. > > The new configuration option let user to enable the memory isolation in need. > By default, OVS uses default dpdk memory regions. > > To isolate the memory regions, DPDK prefix the memory map files with user > input string. This implementation uses the pid of vswitchd process as a memory > map prefix, because its unique in the platform. > > For eg: a vswitchd process with pid '12345' create memory map regions with > prefix 'ovs-12345' in the filesystem. > > The following configuration option is used to enable the feature and changing > this value requires restarting the daemon. > > ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-isolate-mem=true > > Signed-off-by: Sugesh Chandran <[email protected]>
I believe that this patch adds code to ovs-vswitchd to read ovs-vswitchd's own pidfile. I don't understand this. Wouldn't it make more sense to just call getpid()? Thanks, Ben. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
