DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Li Feng <fengli@smartx.com>
Cc: dev@dpdk.org, stable@dpdk.org, kyle@smartx.com,
	lifeng1519@gmail.com, fanyang@smartx.com,
	david.marchand@redhat.com, bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] eal: use madvise to exclude unmapped memory from being dumped
Date: Fri, 24 Apr 2020 12:23:44 +0100	[thread overview]
Message-ID: <06c98fdc-9fc9-27b3-ebb9-e9a93f3a7561@intel.com> (raw)
In-Reply-To: <20200424105016.28974-1-fengli@smartx.com>

On 24-Apr-20 11:50 AM, Li Feng wrote:
> Currently, even though memory is mapped with PROT_NONE, this does not
> cause it to be excluded from core dumps. This is counter-productive,
> because in a lot of cases, this memory will go unused (e.g. when the
> memory subsystem preallocates VA space but hasn't yet mapped physical
> pages into it).
> 
> Use `madvise()` call with MADV_DONTDUMP parameter to exclude the
> unmapped memory from being dumped.
> 
> Signed-off-by: Li Feng <fengli@smartx.com>
> ---
> V2:
> - add support for freebsd.
> - when free_seg is called, mark the memory MADV_DONTDUMP.
> - when alloc_seg is called, mark the memory MADV_DODUMP.

Isn't this v3 now?

> 
>   lib/librte_eal/common/eal_common_memory.c | 26 ++++++++++++++++++++++++++
>   lib/librte_eal/linux/eal_memalloc.c       |  6 ++++++
>   2 files changed, 32 insertions(+)
> 
> diff --git a/lib/librte_eal/common/eal_common_memory.c b/lib/librte_eal/common/eal_common_memory.c
> index cc7d54e0c..83be94a20 100644
> --- a/lib/librte_eal/common/eal_common_memory.c
> +++ b/lib/librte_eal/common/eal_common_memory.c
> @@ -177,6 +177,32 @@ eal_get_virtual_area(void *requested_addr, size_t *size,
>   		after_len = RTE_PTR_DIFF(map_end, aligned_end);
>   		if (after_len > 0)
>   			munmap(aligned_end, after_len);
> +
> +		/*
> +		 * Exclude this pages from a core dump.
> +		 */
> +#ifdef RTE_EXEC_ENV_LINUX
> +		if (madvise(aligned_addr, *size, MADV_DONTDUMP) != 0)
> +			RTE_LOG(DEBUG, EAL, "madvise failed: %s\n",
> +				strerror(errno));
> +#elif RTE_EXEC_ENV_FREEBSD
> +		if (madvise(aligned_addr, *size, MADV_NOCORE) != 0)
> +			RTE_LOG(DEBUG, EAL, "madvise failed: %s\n",
> +				strerror(errno));
> +#endif
> +	} else {
> +		/*
> +		 * Exclude this pages from a core dump.
> +		 */
> +#ifdef RTE_EXEC_ENV_LINUX
> +		if (madvise(mapped_addr, map_sz, MADV_DONTDUMP) != 0)
> +			RTE_LOG(DEBUG, EAL, "madvise failed: %s\n",
> +				strerror(errno));
> +#elif RTE_EXEC_ENV_FREEBSD
> +		if (madvise(mapped_addr, map_sz, MADV_NOCORE) != 0)
> +			RTE_LOG(DEBUG, EAL, "madvise failed: %s\n",
> +				strerror(errno));
> +#endif
>   	}

DRY (Don't Repeat Yourself) :) Probably easier to do "if (!unmap) ..." 
than putting this into two places.

>   
>   	return aligned_addr;
> diff --git a/lib/librte_eal/linux/eal_memalloc.c b/lib/librte_eal/linux/eal_memalloc.c
> index af6d0d023..9d2a6fc6f 100644
> --- a/lib/librte_eal/linux/eal_memalloc.c
> +++ b/lib/librte_eal/linux/eal_memalloc.c
> @@ -571,6 +571,9 @@ alloc_seg(struct rte_memseg *ms, void *addr, int socket_id,
>   		goto resized;
>   	}
>   
> +	if (madvise(addr, alloc_sz, MADV_DODUMP) != 0)
> +		RTE_LOG(DEBUG, EAL, "madvise failed: %s\n", strerror(errno));
> +

See discussion for v2, i believe this is unnecessary.

>   	/* In linux, hugetlb limitations, like cgroup, are
>   	 * enforced at fault time instead of mmap(), even
>   	 * with the option of MAP_POPULATE. Kernel will send
> @@ -687,6 +690,9 @@ free_seg(struct rte_memseg *ms, struct hugepage_info *hi,
>   		return -1;
>   	}
>   
> +	if (madvise(ms->addr, ms->len, MADV_DONTDUMP) != 0)
> +		RTE_LOG(DEBUG, EAL, "madvise failed: %s\n", strerror(errno));
> +
>   	exit_early = false;
>   
>   	/* if we're using anonymous hugepages, nothing to be done */
> 


-- 
Thanks,
Anatoly

  reply	other threads:[~2020-04-24 11:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24 10:50 Li Feng
2020-04-24 11:23 ` Burakov, Anatoly [this message]
2020-04-24 11:36   ` Bruce Richardson
2020-04-24 11:46     ` Burakov, Anatoly
2020-04-24 12:37   ` Li Feng
2020-04-24 12:39 ` [dpdk-dev] [PATCH v4] " Li Feng
2020-04-24 12:53 ` [dpdk-dev] [PATCH v5] " Li Feng
2020-04-24 13:02   ` Bruce Richardson
2020-04-24 13:19 ` [dpdk-dev] [PATCH v6] " Li Feng
2020-04-24 15:20   ` Burakov, Anatoly
2020-04-24 17:33   ` David Marchand

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=06c98fdc-9fc9-27b3-ebb9-e9a93f3a7561@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=fanyang@smartx.com \
    --cc=fengli@smartx.com \
    --cc=kyle@smartx.com \
    --cc=lifeng1519@gmail.com \
    --cc=stable@dpdk.org \
    /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).