From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Cian Ferriter <cian.ferriter@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] lib/librte_ether: change socket_id passed to rte_memzone_reserve
Date: Tue, 27 Jan 2015 10:29:21 +0100 [thread overview]
Message-ID: <8331960.qMyqHR1SLh@xps13> (raw)
In-Reply-To: <1421939108-28666-1-git-send-email-cian.ferriter@intel.com>
Hi,
2015-01-22 15:05, Cian Ferriter:
> Removes the dependency that this memzone reserve has on the
> socket currently running on. Following the socket of the master
> core will yield more predictable results when calling this
> function after initialisation.
You don't describe what is the problem. In another mail, you say
"The original suggestion also fixes the crash that I was seeing because
of memory being reserved from a numa node with no "--socket-mem" allocated."
Please describe it clearly in the commit log.
You should also explain what this rte_memzone_reserve() is for,
and what are the incidences of your changes.
Thanks
--
Thomas
> @@ -184,7 +184,7 @@ rte_eth_dev_data_alloc(void)
> if (rte_eal_process_type() == RTE_PROC_PRIMARY){
> mz = rte_memzone_reserve(MZ_RTE_ETH_DEV_DATA,
> RTE_MAX_ETHPORTS * sizeof(*rte_eth_dev_data),
> - rte_socket_id(), flags);
> + rte_lcore_to_socket_id(rte_get_master_lcore()), flags);
next prev parent reply other threads:[~2015-01-27 9:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 15:05 Cian Ferriter
2015-01-27 9:29 ` Thomas Monjalon [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-01-13 9:22 Cian Ferriter
2015-01-13 9:23 ` Ferriter, Cian
2015-01-13 13:55 ` Bruce Richardson
2015-01-13 18:05 ` Ferriter, Cian
2015-01-14 10:09 ` Bruce Richardson
2015-01-19 18:38 ` Ferriter, Cian
2015-01-22 9:56 ` Ferriter, Cian
2015-01-22 11:26 ` Bruce Richardson
2015-01-13 23:24 ` Stephen Hemminger
2015-01-14 10:13 ` Bruce Richardson
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=8331960.qMyqHR1SLh@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=cian.ferriter@intel.com \
--cc=dev@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).