From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: dev@dpdk.org
Cc: stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] malloc: fix duplicate mem event notification
Date: Thu, 29 Nov 2018 15:36:56 +0000 [thread overview]
Message-ID: <d1f8a16c-7987-9488-dd27-014e9ec5a7b3@intel.com> (raw)
In-Reply-To: <a3807707cec73b13b25cdd623440fbcb61f02134.1543501068.git.anatoly.burakov@intel.com>
On 29-Nov-18 3:18 PM, Anatoly Burakov wrote:
> We already trigger a mem event notification inside the walk function,
> no need to do it twice.
>
> Fixes: f32c7c9de961 ("malloc: enable event callbacks for external memory")
> Cc: stable@dpdk.org
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> ---
> lib/librte_eal/common/rte_malloc.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/lib/librte_eal/common/rte_malloc.c b/lib/librte_eal/common/rte_malloc.c
> index 0da5ad5e8..750a83c2c 100644
> --- a/lib/librte_eal/common/rte_malloc.c
> +++ b/lib/librte_eal/common/rte_malloc.c
> @@ -518,10 +518,6 @@ sync_memory(const char *heap_name, void *va_addr, size_t len, bool attach)
> rte_errno = -wa.result;
> ret = -1;
> } else {
> - /* notify all subscribers that a new memory area was added */
> - if (attach)
> - eal_memalloc_mem_event_notify(RTE_MEM_EVENT_ALLOC,
> - va_addr, len);
> ret = 0;
> }
> unlock:
>
Oops, dupe.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-11-29 15:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 14:21 [dpdk-stable] " Anatoly Burakov
2018-11-29 14:54 ` [dpdk-stable] [dpdk-dev] " Wiles, Keith
2018-11-29 15:36 ` Burakov, Anatoly
2018-11-29 15:47 ` Wiles, Keith
2018-11-29 17:05 ` Ferruh Yigit
2018-11-29 15:18 ` [dpdk-stable] " Anatoly Burakov
2018-11-29 15:36 ` Burakov, Anatoly [this message]
2018-12-11 16:48 ` [dpdk-stable] [PATCH v2] " Anatoly Burakov
2018-12-20 14:29 ` Thomas Monjalon
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=d1f8a16c-7987-9488-dd27-014e9ec5a7b3@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--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).