DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Bruce Richardson <bruce.richardson@intel.com>,
	Kamaraj P <pkamaraj@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK hugepage memory fragmentation
Date: Fri, 10 Jul 2020 16:44:19 +0100
Message-ID: <d9d25343-e6ce-e77f-6c29-bf31ace74942@intel.com> (raw)
In-Reply-To: <20200710102837.GB684@bricha3-MOBL.ger.corp.intel.com>

On 10-Jul-20 11:28 AM, Bruce Richardson wrote:
> On Fri, Jul 10, 2020 at 02:52:16PM +0530, Kamaraj P wrote:
>> Hello All,
>>
>> We are running to run DPDK based application in a container mode,
>> When we do multiple start/stop of our container application, the DPDK
>> initialization seems to be failing.
>> This is because the hugepage memory fragementated and is not able to find
>> the continuous allocation of the memory to initialize the buffer in the
>> dpdk init.
>>
>> As part of the cleanup of the container, we do call rte_eal_cleanup() to
>> cleanup the memory w.r.t our application. However after iterations we still
>> see the memory allocation failure due to the fragmentation issue.
>>
>> We also tried to set the "--huge-unlink" as an argument before when we
>> called the rte_eal_init() and it did not help.
>>
>> Could you please suggest if there is an option or any existing patches
>> available to clean up the memory to avoid fragmentation issues in the
>> future.
>>
>> Please advise.
>>
> What version of DPDK are you using, and what kernel driver for NIC
> interfacing are you using?
> DPDK versions since 18.05 should be more forgiving of fragmented memory,
> especially if using the vfio-pci kernel driver.
> 

This sounds odd, to be honest.

Unless you're allocating huge chunks of IOVA-contiguous memory, 
fragmentation shouldn't be an issue. How did you determine that this was 
in fact due to fragmentation?

> Regards,
> /Bruce
> 


-- 
Thanks,
Anatoly

  reply	other threads:[~2020-07-10 15:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10  9:22 Kamaraj P
2020-07-10 10:28 ` Bruce Richardson
2020-07-10 15:44   ` Burakov, Anatoly [this message]
2020-07-11  7:51     ` Kamaraj P
2020-07-13  9:27       ` Burakov, Anatoly
2020-07-27 15:30         ` Kamaraj P
2020-07-28 10:10           ` Burakov, Anatoly
2020-09-16  4:32             ` Kamaraj P
2020-09-16 11:19               ` Burakov, Anatoly
2020-09-16 11:47                 ` Burakov, Anatoly

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=d9d25343-e6ce-e77f-6c29-bf31ace74942@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=pkamaraj@gmail.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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git