From: Thomas Monjalon <thomas@monjalon.net>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: stable@dpdk.org, dev@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] malloc: fix documentation for realloc
Date: Wed, 27 Mar 2019 12:03:30 +0100 [thread overview]
Message-ID: <2037565.XbdSNCcqL8@xps> (raw)
Message-ID: <20190327110330.iHTarTHw-dWye0i9LyuNwQzN3Pz7Ef2nr-1kgfo1P6Q@z> (raw)
In-Reply-To: <a7fefd2eb6cf6ffb8346e032b4f0cdac69fd5e35.1550849324.git.anatoly.burakov@intel.com>
22/02/2019 16:29, Anatoly Burakov:
> The documentation for rte_realloc claims that the resized area
> will always reside on the same NUMA node. This is not actually
> the case - while *resized* area will be on the same NUMA node,
> if resizing the area is not possible, then the memory will be
> reallocated using rte_malloc(), which can allocate memory on
> another NUMA node, depending on which lcore rte_realloc() was
> called from and which NUMA nodes have memory available.
>
> Fix the API doc to match the actual code of rte_realloc().
>
> Fixes: af75078fece3 ("first public release")
> Cc: stable@dpdk.org
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
Applied, thanks
next prev parent reply other threads:[~2019-03-27 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 15:29 [dpdk-dev] " Anatoly Burakov
2019-03-27 11:03 ` Thomas Monjalon [this message]
2019-03-27 11:03 ` [dpdk-dev] [dpdk-stable] " 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=2037565.XbdSNCcqL8@xps \
--to=thomas@monjalon.net \
--cc=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).