[ovs-git] [openvswitch/ovs] 4257ef: dpdk: Use dynamic string for socket-mem construction.

Ilya Maximets noreply at github.com
Fri Feb 1 13:47:00 UTC 2019


  Branch: refs/heads/branch-2.11
  Home:   https://github.com/openvswitch/ovs
  Commit: 4257ef05b8e1847b3c5558f137e8eea553e8ba07
      https://github.com/openvswitch/ovs/commit/4257ef05b8e1847b3c5558f137e8eea553e8ba07
  Author: Ilya Maximets <i.maximets at samsung.com>
  Date:   2019-02-01 (Fri, 01 Feb 2019)

  Changed paths:
    M lib/dpdk.c

  Log Message:
  -----------
  dpdk: Use dynamic string for socket-mem construction.

No need to allocate memory and use 'strcat' direcly.
'dynamic-string' could do this for us.

Signed-off-by: Ilya Maximets <i.maximets at samsung.com>
Acked-by: Aaron Conole <aconole at redhat.com>
Signed-off-by: Ian Stokes <ian.stokes at intel.com>


  Commit: aadf6d04840a2519136daee431dbe5058e1c57a7
      https://github.com/openvswitch/ovs/commit/aadf6d04840a2519136daee431dbe5058e1c57a7
  Author: Ilya Maximets <i.maximets at samsung.com>
  Date:   2019-02-01 (Fri, 01 Feb 2019)

  Changed paths:
    M lib/dpdk.c

  Log Message:
  -----------
  dpdk: Use svec instead of re-inventing.

No need to implement dynamic vector to store arguments.
'svec' perfectly covers all the needed functionality.

Signed-off-by: Ilya Maximets <i.maximets at samsung.com>
Acked-by: Aaron Conole <aconole at redhat.com>
Signed-off-by: Ian Stokes <ian.stokes at intel.com>


  Commit: fabb9e37667a8eae7279847d04120b11625e8d5b
      https://github.com/openvswitch/ovs/commit/fabb9e37667a8eae7279847d04120b11625e8d5b
  Author: Ilya Maximets <i.maximets at samsung.com>
  Date:   2019-02-01 (Fri, 01 Feb 2019)

  Changed paths:
    M NEWS
    M lib/dpdk.c
    M vswitchd/vswitch.xml

  Log Message:
  -----------
  dpdk: Limit DPDK memory usage.

Since 18.05 release, DPDK moved to dynamic memory model in which
hugepages could be allocated on demand. At the same time '--socket-mem'
option was re-defined as a size of pre-allocated memory, i.e. memory
that should be allocated at startup and could not be freed.
So, DPDK with a new memory model could allocate more hugepage memory
than specified in '--socket-mem' or '-m' options.

This change adds new configurable 'other_config:dpdk-socket-limit'
which could be used to limit the ammount of memory DPDK could use.
It uses new DPDK option '--socket-limit'.
Ex.:

  ovs-vsctl set Open_vSwitch . other_config:dpdk-socket-limit="1024,1024"

Also, in order to preserve old behaviour, if '--socket-limit' is not
specified, it will be defaulted to the amount of memory specified by
'--socket-mem' option, i.e. OVS will not be able to allocate more.
This is needed, for example, to disallow OVS to allocate more memory
than reserved for it by Nova in OpenStack installations.

Signed-off-by: Ilya Maximets <i.maximets at samsung.com>
Signed-off-by: Ian Stokes <ian.stokes at intel.com>


Compare: https://github.com/openvswitch/ovs/compare/d3a10db4fd38...fabb9e37667a


More information about the git mailing list