DPDK patches and discussions
 help / color / mirror / Atom feed
From: Suanming Mou <suanmingm@mellanox.com>
To: Matan Azrad <matan@mellanox.com>, Ori Kam <orika@mellanox.com>,
	Slava Ovsiienko <viacheslavo@mellanox.com>
Cc: dev@dpdk.org, waela@mellanox.com, rasland@mellanox.com
Subject: [dpdk-dev] [RFC] net/mlx5: add reclaim_mem_mode devarg
Date: Fri, 8 May 2020 18:33:07 +0800	[thread overview]
Message-ID: <ef2fe5c2-6aeb-8e03-99cb-ada76cd44d9f@mellanox.com> (raw)

Currently, when flow destroyed, some memory resources may still be kept 
as cached to help next time create flow more efficiently.

Some system may need the resources to be more flexible with flow create 
and destroy.  After peak time, with millions of flows destroyed, the 
system would prefer the resources to be reclaimed completely, no cache 
is needed. Then the resources can be allocated and used by other 
components. The system is not so sensitive about the flow insertion 
rate, but more care about the resources.

Both DPDK mlx5 PMD driver and the low level component rdma-core have 
provided the flow resources to be configured cached or not, but there is 
no APIs or parameters exposed to user to configure the flow resources 
cache mode. In this case, introduce a new PMD devarg to let user 
configure the flow resources cache mode will be helpful.

The intention is to add a new "reclaim_mem_mode" to help user configure 
if the destroyed flows' cache resources should be kept or not.
Their will be three mode can be chosen:
1. 0(none). It means the flow resources will be cached as usual. The 
resources will be cached, helpful with flow insertion rate.
2. 1(light). It will only enable the DPDK PMD level resources reclaim.
3. 2(aggressive). Both DPDK PMD level and rdma-core low level will be 
configured as reclaimed mode.

With these three mode, user can configure the resources cache mode with 
different level.
The sample configuration as below:
./testpmd -n 4  -w 0000:d8:00.0,reclaim_mem_mode=2 -- --burst=64 
--mbcache=512 -i  --nb-cores=7

Thanks,
SuanmingMou

                 reply	other threads:[~2020-05-08 10:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ef2fe5c2-6aeb-8e03-99cb-ada76cd44d9f@mellanox.com \
    --to=suanmingm@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=matan@mellanox.com \
    --cc=orika@mellanox.com \
    --cc=rasland@mellanox.com \
    --cc=viacheslavo@mellanox.com \
    --cc=waela@mellanox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).