From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Tomasz Jozwiak <tomaszx.jozwiak@intel.com>,
dev@dpdk.org, fiona.trahe@intel.com
Subject: Re: [dpdk-dev] [PATCH] malloc: add rte_realloc_socket function
Date: Tue, 5 Mar 2019 10:04:16 +0000 [thread overview]
Message-ID: <bd0efaa4-271e-8b98-adc1-52ce8412d666@intel.com> (raw)
In-Reply-To: <1551429976-16297-1-git-send-email-tomaszx.jozwiak@intel.com>
On 01-Mar-19 8:46 AM, Tomasz Jozwiak wrote:
> Currently, rte_realloc will not respect original allocation's
> NUMA node when memory cannot be resized, and there is no
> NUMA-aware equivalent of rte_realloc. This patch adds such a function.
>
> The new API will ensure that reallocated memory stays on
> requested NUMA node, as well as allow moving allocated memory
> to a different NUMA node.
>
> Signed-off-by: Tomasz Jozwiak <tomaszx.jozwiak@intel.com>
> ---
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2019-03-05 10:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 8:46 Tomasz Jozwiak
2019-03-05 10:04 ` Burakov, Anatoly [this message]
2019-03-23 15:57 ` Thomas Monjalon
2019-03-23 15:57 ` 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=bd0efaa4-271e-8b98-adc1-52ce8412d666@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=tomaszx.jozwiak@intel.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).