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
Subject: Re: [dpdk-dev] [PATCH] mem: mark pages as not accessed when returning back to memory pool
Date: Fri, 24 Apr 2020 12:25:49 +0100	[thread overview]
Message-ID: <2812cdbf-7761-42fd-f764-76d90aad5f6d@intel.com> (raw)
In-Reply-To: <20200424104205.26846-1-fengli@smartx.com>

On 24-Apr-20 11:42 AM, Li Feng wrote:
> Commit 8a4baf06c17a ("mem: mark pages as not accessed when reserving VA")
> has mapped the initialized memory with PROT_NONE, and when it's unmapped,
> eal_memalloc.c should remmap the anonymous memory with PROT_NONE too.
> 
> Signed-off-by: Li Feng <fengli@smartx.com>
> ---
>   lib/librte_eal/linux/eal_memalloc.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/lib/librte_eal/linux/eal_memalloc.c b/lib/librte_eal/linux/eal_memalloc.c
> index 9d2a6fc6f..64a2b44c1 100644
> --- a/lib/librte_eal/linux/eal_memalloc.c
> +++ b/lib/librte_eal/linux/eal_memalloc.c
> @@ -683,7 +683,7 @@ free_seg(struct rte_memseg *ms, struct hugepage_info *hi,
>   	/* erase page data */
>   	memset(ms->addr, 0, ms->len);
>   
> -	if (mmap(ms->addr, ms->len, PROT_READ,
> +	if (mmap(ms->addr, ms->len, PROT_NONE,
>   			MAP_PRIVATE | MAP_ANONYMOUS | MAP_FIXED, -1, 0) ==
>   				MAP_FAILED) {
>   		RTE_LOG(DEBUG, EAL, "couldn't unmap page\n");
> 

Fixes: 8a4baf06c17a ("mem: mark pages as not accessed when reserving VA")
Cc: david.marchand@redhat.com
Cc: stable@dpdk.org

Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>

-- 
Thanks,
Anatoly

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24 10:42 Li Feng
2020-04-24 11:25 ` Burakov, Anatoly [this message]
2020-04-24 17:10 ` David Marchand
2020-04-26  2:51   ` Li Feng

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=2812cdbf-7761-42fd-f764-76d90aad5f6d@intel.com \
    --to=anatoly.burakov@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).