From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: "Singh, Jasvinder" <jasvinder.singh@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] librte_sched: allocate memory on the given socket id
Date: Thu, 27 Sep 2018 17:52:24 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891268E7C2FA9@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <20180927171045.103407-1-jasvinder.singh@intel.com>
> -----Original Message-----
> From: Singh, Jasvinder
> Sent: Thursday, September 27, 2018 6:11 PM
> To: dev@dpdk.org
> Cc: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> Subject: [PATCH] librte_sched: allocate memory on the given socket id
>
> Replace rte_zmalloc() with rte_zmalloc_socket() to allocate
> memory on the socket id provided by the application.
>
> Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
> ---
> lib/librte_sched/rte_sched.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/lib/librte_sched/rte_sched.c b/lib/librte_sched/rte_sched.c
> index 9269e5c71..328c983b4 100644
> --- a/lib/librte_sched/rte_sched.c
> +++ b/lib/librte_sched/rte_sched.c
> @@ -633,7 +633,8 @@ rte_sched_port_config(struct
> rte_sched_port_params *params)
> return NULL;
>
> /* Allocate memory to store the data structures */
> - port = rte_zmalloc("qos_params", mem_size,
> RTE_CACHE_LINE_SIZE);
> + port = rte_zmalloc_socket("qos_params", mem_size,
> RTE_CACHE_LINE_SIZE,
> + params->socket);
> if (port == NULL)
> return NULL;
>
> --
> 2.17.1
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
next prev parent reply other threads:[~2018-09-27 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 17:10 Jasvinder Singh
2018-09-27 17:52 ` Dumitrescu, Cristian [this message]
2018-10-08 15:57 ` Dumitrescu, Cristian
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=3EB4FA525960D640B5BDFFD6A3D891268E7C2FA9@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@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).