| Message ID | D9B9B7EDAA4D17468E64B453458633E4044E9D21@IRSMSX108.ger.corp.intel.com (mailing list archive) |
|---|---|
| State | Superseded, archived |
| Headers |
Return-Path: <dev-bounces@dpdk.org> X-Original-To: patchwork@dpdk.org Delivered-To: patchwork@dpdk.org Received: from [92.243.14.124] (localhost [IPv6:::1]) by dpdk.org (Postfix) with ESMTP id 3069E5A74; Tue, 13 Jan 2015 10:23:27 +0100 (CET) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 19FE85A71 for <dev@dpdk.org>; Tue, 13 Jan 2015 10:23:18 +0100 (CET) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP; 13 Jan 2015 01:20:38 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.07,748,1413270000"; d="scan'208";a="636509426" Received: from irsmsx101.ger.corp.intel.com ([163.33.3.153]) by orsmga001.jf.intel.com with ESMTP; 13 Jan 2015 01:23:17 -0800 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.71]) by IRSMSX101.ger.corp.intel.com ([169.254.1.126]) with mapi id 14.03.0195.001; Tue, 13 Jan 2015 09:23:16 +0000 From: "Ferriter, Cian" <cian.ferriter@intel.com> To: "dev@dpdk.org" <dev@dpdk.org> Thread-Topic: [PATCH] lib/librte_ether: change socket_id passed to rte_memzone_reserve Thread-Index: AQHQLxJxCtZNxstVx0ajqB3SBqs+d5y9xuPQ Date: Tue, 13 Jan 2015 09:23:16 +0000 Message-ID: <D9B9B7EDAA4D17468E64B453458633E4044E9D21@IRSMSX108.ger.corp.intel.com> References: <1421140920-9964-1-git-send-email-cian.ferriter@intel.com> In-Reply-To: <1421140920-9964-1-git-send-email-cian.ferriter@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH] lib/librte_ether: change socket_id passed to rte_memzone_reserve X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> |
Commit Message
Cian Ferriter
Jan. 13, 2015, 9:23 a.m. UTC
Passing a socket id of "rte_socket_id()" can cause problems in non DPDK applications as there is a dependency on the current logical core we are running on.
Passing " rte_lcore_to_socket_id(rte_get_master_lcore())" as the socket id to rte_memzone_reserve resolves these issues as the master lcore doesn't change.
-----Original Message-----
From: Ferriter, Cian
Sent: Tuesday, January 13, 2015 9:22 AM
To: dev@dpdk.org
Cc: Ferriter, Cian
Subject: [PATCH] lib/librte_ether: change socket_id passed to rte_memzone_reserve
Change the socket id that is passed to rte_memzone_reserve from the socket id of current logical core to the socket id of the master_lcore.
---
lib/librte_ether/rte_ethdev.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-) mode change 100644 => 100755 lib/librte_ether/rte_ethdev.c
--
1.7.4.1
Comments
On Tue, Jan 13, 2015 at 09:23:16AM +0000, Ferriter, Cian wrote: > Passing a socket id of "rte_socket_id()" can cause problems in non DPDK applications as there is a dependency on the current logical core we are running on. > Passing " rte_lcore_to_socket_id(rte_get_master_lcore())" as the socket id to rte_memzone_reserve resolves these issues as the master lcore doesn't change. > The only trouble is that when affinitizing the memory for the NICs to the socket of the master lcore, it gives us no way to correctly configure an app to use NICs connected to two different sockets on the one system. All memory for all NICs will end up on the same socket. Two possible alternative solutions: 1) affinitize memory to the socket the NIC is connected to 2) add a socket parameter to the API calls to allow the user complete control over their memory allocations Obviously the second one breaks backward compatibility (assume we modify existing API call), but is more powerful. Thoughts? /Bruce > -----Original Message----- > From: Ferriter, Cian > Sent: Tuesday, January 13, 2015 9:22 AM > To: dev@dpdk.org > Cc: Ferriter, Cian > Subject: [PATCH] lib/librte_ether: change socket_id passed to rte_memzone_reserve > > Change the socket id that is passed to rte_memzone_reserve from the socket id of current logical core to the socket id of the master_lcore. > --- > lib/librte_ether/rte_ethdev.c | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) mode change 100644 => 100755 lib/librte_ether/rte_ethdev.c > > diff --git a/lib/librte_ether/rte_ethdev.c b/lib/librte_ether/rte_ethdev.c old mode 100644 new mode 100755 index 95f2ceb..835540d > --- a/lib/librte_ether/rte_ethdev.c > +++ b/lib/librte_ether/rte_ethdev.c > @@ -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); > } else > mz = rte_memzone_lookup(MZ_RTE_ETH_DEV_DATA); > if (mz == NULL) > -- > 1.7.4.1 >
Comments on alternative solutions: 1) how would this solution work when there is no NIC present, and "rte_eth_from_rings" is called? Here, could you have an else where the socket id of the master core is passed to the "memzone_reserve"? 2) how would you advise making this change? I have looked at where "rte_eth_dev_allocate" is being called and in all but one case, there is a "numa_id" that could be passed in. This isn't the case for " rte_eth_dev_init" however, is there an easy solution for this? Would there now need to be an "rte_eth_dev_data" struct for each socket that there is a NIC attached to, reserving memory from that socket? Cian -----Original Message----- From: Richardson, Bruce Sent: Tuesday, January 13, 2015 1:56 PM To: Ferriter, Cian Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH] lib/librte_ether: change socket_id passed to rte_memzone_reserve On Tue, Jan 13, 2015 at 09:23:16AM +0000, Ferriter, Cian wrote: > Passing a socket id of "rte_socket_id()" can cause problems in non DPDK applications as there is a dependency on the current logical core we are running on. > Passing " rte_lcore_to_socket_id(rte_get_master_lcore())" as the socket id to rte_memzone_reserve resolves these issues as the master lcore doesn't change. > The only trouble is that when affinitizing the memory for the NICs to the socket of the master lcore, it gives us no way to correctly configure an app to use NICs connected to two different sockets on the one system. All memory for all NICs will end up on the same socket. Two possible alternative solutions: 1) affinitize memory to the socket the NIC is connected to 2) add a socket parameter to the API calls to allow the user complete control over their memory allocations Obviously the second one breaks backward compatibility (assume we modify existing API call), but is more powerful. Thoughts? /Bruce > -----Original Message----- > From: Ferriter, Cian > Sent: Tuesday, January 13, 2015 9:22 AM > To: dev@dpdk.org > Cc: Ferriter, Cian > Subject: [PATCH] lib/librte_ether: change socket_id passed to > rte_memzone_reserve > > Change the socket id that is passed to rte_memzone_reserve from the socket id of current logical core to the socket id of the master_lcore. > --- > lib/librte_ether/rte_ethdev.c | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) mode change 100644 > => 100755 lib/librte_ether/rte_ethdev.c > > diff --git a/lib/librte_ether/rte_ethdev.c > b/lib/librte_ether/rte_ethdev.c old mode 100644 new mode 100755 index > 95f2ceb..835540d > --- a/lib/librte_ether/rte_ethdev.c > +++ b/lib/librte_ether/rte_ethdev.c > @@ -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); > } else > mz = rte_memzone_lookup(MZ_RTE_ETH_DEV_DATA); > if (mz == NULL) > -- > 1.7.4.1 >
On Tue, Jan 13, 2015 at 06:05:25PM +0000, Ferriter, Cian wrote: > Comments on alternative solutions: > 1) how would this solution work when there is no NIC present, and "rte_eth_from_rings" is called? Here, could you have an else where the socket id of the master core is passed to the "memzone_reserve"? > 2) how would you advise making this change? I have looked at where "rte_eth_dev_allocate" is being called and in all but one case, there is a "numa_id" that could be passed in. This isn't the case for " rte_eth_dev_init" however, is there an easy solution for this? Would there now need to be an "rte_eth_dev_data" struct for each socket that there is a NIC attached to, reserving memory from that socket? > > Cian While I think the issues you highlight can probably be overcome, I'm not so sure any more how much it matters what numa node this is allocated on. The ethdev data for any port in use by a port should be in the cache. In that case, if it doesn't matter, your original suggestion would work fine. /Bruce > > -----Original Message----- > From: Richardson, Bruce > Sent: Tuesday, January 13, 2015 1:56 PM > To: Ferriter, Cian > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH] lib/librte_ether: change socket_id passed to rte_memzone_reserve > > On Tue, Jan 13, 2015 at 09:23:16AM +0000, Ferriter, Cian wrote: > > Passing a socket id of "rte_socket_id()" can cause problems in non DPDK applications as there is a dependency on the current logical core we are running on. > > Passing " rte_lcore_to_socket_id(rte_get_master_lcore())" as the socket id to rte_memzone_reserve resolves these issues as the master lcore doesn't change. > > > > The only trouble is that when affinitizing the memory for the NICs to the socket of the master lcore, it gives us no way to correctly configure an app to use NICs connected to two different sockets on the one system. All memory for all NICs will end up on the same socket. Two possible alternative solutions: > 1) affinitize memory to the socket the NIC is connected to > 2) add a socket parameter to the API calls to allow the user complete control over their memory allocations > > Obviously the second one breaks backward compatibility (assume we modify existing API call), but is more powerful. > > Thoughts? > > /Bruce > > > -----Original Message----- > > From: Ferriter, Cian > > Sent: Tuesday, January 13, 2015 9:22 AM > > To: dev@dpdk.org > > Cc: Ferriter, Cian > > Subject: [PATCH] lib/librte_ether: change socket_id passed to > > rte_memzone_reserve > > > > Change the socket id that is passed to rte_memzone_reserve from the socket id of current logical core to the socket id of the master_lcore. > > --- > > lib/librte_ether/rte_ethdev.c | 2 +- > > 1 files changed, 1 insertions(+), 1 deletions(-) mode change 100644 > > => 100755 lib/librte_ether/rte_ethdev.c > > > > diff --git a/lib/librte_ether/rte_ethdev.c > > b/lib/librte_ether/rte_ethdev.c old mode 100644 new mode 100755 index > > 95f2ceb..835540d > > --- a/lib/librte_ether/rte_ethdev.c > > +++ b/lib/librte_ether/rte_ethdev.c > > @@ -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); > > } else > > mz = rte_memzone_lookup(MZ_RTE_ETH_DEV_DATA); > > if (mz == NULL) > > -- > > 1.7.4.1 > >
I would be happy with the original suggestion. If the ethdev data for a port in use is in cache it removes the performance concern associated the current setup and my fix. 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. Cian -----Original Message----- From: Richardson, Bruce Sent: Wednesday, January 14, 2015 10:10 AM To: Ferriter, Cian Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH] lib/librte_ether: change socket_id passed to rte_memzone_reserve On Tue, Jan 13, 2015 at 06:05:25PM +0000, Ferriter, Cian wrote: > Comments on alternative solutions: > 1) how would this solution work when there is no NIC present, and "rte_eth_from_rings" is called? Here, could you have an else where the socket id of the master core is passed to the "memzone_reserve"? > 2) how would you advise making this change? I have looked at where "rte_eth_dev_allocate" is being called and in all but one case, there is a "numa_id" that could be passed in. This isn't the case for " rte_eth_dev_init" however, is there an easy solution for this? Would there now need to be an "rte_eth_dev_data" struct for each socket that there is a NIC attached to, reserving memory from that socket? > > Cian While I think the issues you highlight can probably be overcome, I'm not so sure any more how much it matters what numa node this is allocated on. The ethdev data for any port in use by a port should be in the cache. In that case, if it doesn't matter, your original suggestion would work fine. /Bruce > > -----Original Message----- > From: Richardson, Bruce > Sent: Tuesday, January 13, 2015 1:56 PM > To: Ferriter, Cian > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH] lib/librte_ether: change socket_id > passed to rte_memzone_reserve > > On Tue, Jan 13, 2015 at 09:23:16AM +0000, Ferriter, Cian wrote: > > Passing a socket id of "rte_socket_id()" can cause problems in non DPDK applications as there is a dependency on the current logical core we are running on. > > Passing " rte_lcore_to_socket_id(rte_get_master_lcore())" as the socket id to rte_memzone_reserve resolves these issues as the master lcore doesn't change. > > > > The only trouble is that when affinitizing the memory for the NICs to the socket of the master lcore, it gives us no way to correctly configure an app to use NICs connected to two different sockets on the one system. All memory for all NICs will end up on the same socket. Two possible alternative solutions: > 1) affinitize memory to the socket the NIC is connected to > 2) add a socket parameter to the API calls to allow the user complete > control over their memory allocations > > Obviously the second one breaks backward compatibility (assume we modify existing API call), but is more powerful. > > Thoughts? > > /Bruce > > > -----Original Message----- > > From: Ferriter, Cian > > Sent: Tuesday, January 13, 2015 9:22 AM > > To: dev@dpdk.org > > Cc: Ferriter, Cian > > Subject: [PATCH] lib/librte_ether: change socket_id passed to > > rte_memzone_reserve > > > > Change the socket id that is passed to rte_memzone_reserve from the socket id of current logical core to the socket id of the master_lcore. > > --- > > lib/librte_ether/rte_ethdev.c | 2 +- > > 1 files changed, 1 insertions(+), 1 deletions(-) mode change > > 100644 => 100755 lib/librte_ether/rte_ethdev.c > > > > diff --git a/lib/librte_ether/rte_ethdev.c > > b/lib/librte_ether/rte_ethdev.c old mode 100644 new mode 100755 > > index 95f2ceb..835540d > > --- a/lib/librte_ether/rte_ethdev.c > > +++ b/lib/librte_ether/rte_ethdev.c > > @@ -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); > > } else > > mz = rte_memzone_lookup(MZ_RTE_ETH_DEV_DATA); > > if (mz == NULL) > > -- > > 1.7.4.1 > >
Hey guys, I just wanted to ask is there anything more that can be done with this patch or is it in an acceptable state for pushing? Cian -----Original Message----- From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ferriter, Cian Sent: Monday, January 19, 2015 6:39 PM To: Richardson, Bruce Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH] lib/librte_ether: change socket_id passed to rte_memzone_reserve I would be happy with the original suggestion. If the ethdev data for a port in use is in cache it removes the performance concern associated the current setup and my fix. 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. Cian -----Original Message----- From: Richardson, Bruce Sent: Wednesday, January 14, 2015 10:10 AM To: Ferriter, Cian Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH] lib/librte_ether: change socket_id passed to rte_memzone_reserve On Tue, Jan 13, 2015 at 06:05:25PM +0000, Ferriter, Cian wrote: > Comments on alternative solutions: > 1) how would this solution work when there is no NIC present, and "rte_eth_from_rings" is called? Here, could you have an else where the socket id of the master core is passed to the "memzone_reserve"? > 2) how would you advise making this change? I have looked at where "rte_eth_dev_allocate" is being called and in all but one case, there is a "numa_id" that could be passed in. This isn't the case for " rte_eth_dev_init" however, is there an easy solution for this? Would there now need to be an "rte_eth_dev_data" struct for each socket that there is a NIC attached to, reserving memory from that socket? > > Cian While I think the issues you highlight can probably be overcome, I'm not so sure any more how much it matters what numa node this is allocated on. The ethdev data for any port in use by a port should be in the cache. In that case, if it doesn't matter, your original suggestion would work fine. /Bruce > > -----Original Message----- > From: Richardson, Bruce > Sent: Tuesday, January 13, 2015 1:56 PM > To: Ferriter, Cian > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH] lib/librte_ether: change socket_id > passed to rte_memzone_reserve > > On Tue, Jan 13, 2015 at 09:23:16AM +0000, Ferriter, Cian wrote: > > Passing a socket id of "rte_socket_id()" can cause problems in non DPDK applications as there is a dependency on the current logical core we are running on. > > Passing " rte_lcore_to_socket_id(rte_get_master_lcore())" as the socket id to rte_memzone_reserve resolves these issues as the master lcore doesn't change. > > > > The only trouble is that when affinitizing the memory for the NICs to the socket of the master lcore, it gives us no way to correctly configure an app to use NICs connected to two different sockets on the one system. All memory for all NICs will end up on the same socket. Two possible alternative solutions: > 1) affinitize memory to the socket the NIC is connected to > 2) add a socket parameter to the API calls to allow the user complete > control over their memory allocations > > Obviously the second one breaks backward compatibility (assume we modify existing API call), but is more powerful. > > Thoughts? > > /Bruce > > > -----Original Message----- > > From: Ferriter, Cian > > Sent: Tuesday, January 13, 2015 9:22 AM > > To: dev@dpdk.org > > Cc: Ferriter, Cian > > Subject: [PATCH] lib/librte_ether: change socket_id passed to > > rte_memzone_reserve > > > > Change the socket id that is passed to rte_memzone_reserve from the socket id of current logical core to the socket id of the master_lcore. > > --- > > lib/librte_ether/rte_ethdev.c | 2 +- > > 1 files changed, 1 insertions(+), 1 deletions(-) mode change > > 100644 => 100755 lib/librte_ether/rte_ethdev.c > > > > diff --git a/lib/librte_ether/rte_ethdev.c > > b/lib/librte_ether/rte_ethdev.c old mode 100644 new mode 100755 > > index 95f2ceb..835540d > > --- a/lib/librte_ether/rte_ethdev.c > > +++ b/lib/librte_ether/rte_ethdev.c > > @@ -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); > > } else > > mz = rte_memzone_lookup(MZ_RTE_ETH_DEV_DATA); > > if (mz == NULL) > > -- > > 1.7.4.1 > >
On Thu, Jan 22, 2015 at 09:56:48AM +0000, Ferriter, Cian wrote: > Hey guys, > > I just wanted to ask is there anything more that can be done with this patch or is it in an acceptable state for pushing? > > Cian At this stage I think I'm ok with the patch contents, unless anyone else objects. However, your patch submission is missing the sign-off line needed before it can be committed. Can you please resubmit with the proper sign-off. [See http://www.dpdk.org/dev] Regards, /Bruce > > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ferriter, Cian > Sent: Monday, January 19, 2015 6:39 PM > To: Richardson, Bruce > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH] lib/librte_ether: change socket_id passed to rte_memzone_reserve > > I would be happy with the original suggestion. If the ethdev data for a port in use is in cache it removes the performance concern associated the current setup and my fix. 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. > > Cian > > -----Original Message----- > From: Richardson, Bruce > Sent: Wednesday, January 14, 2015 10:10 AM > To: Ferriter, Cian > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH] lib/librte_ether: change socket_id passed to rte_memzone_reserve > > On Tue, Jan 13, 2015 at 06:05:25PM +0000, Ferriter, Cian wrote: > > Comments on alternative solutions: > > 1) how would this solution work when there is no NIC present, and "rte_eth_from_rings" is called? Here, could you have an else where the socket id of the master core is passed to the "memzone_reserve"? > > 2) how would you advise making this change? I have looked at where "rte_eth_dev_allocate" is being called and in all but one case, there is a "numa_id" that could be passed in. This isn't the case for " rte_eth_dev_init" however, is there an easy solution for this? Would there now need to be an "rte_eth_dev_data" struct for each socket that there is a NIC attached to, reserving memory from that socket? > > > > Cian > > While I think the issues you highlight can probably be overcome, I'm not so sure any more how much it matters what numa node this is allocated on. The ethdev data for any port in use by a port should be in the cache. In that case, if it doesn't matter, your original suggestion would work fine. > > /Bruce > > > > > -----Original Message----- > > From: Richardson, Bruce > > Sent: Tuesday, January 13, 2015 1:56 PM > > To: Ferriter, Cian > > Cc: dev@dpdk.org > > Subject: Re: [dpdk-dev] [PATCH] lib/librte_ether: change socket_id > > passed to rte_memzone_reserve > > > > On Tue, Jan 13, 2015 at 09:23:16AM +0000, Ferriter, Cian wrote: > > > Passing a socket id of "rte_socket_id()" can cause problems in non DPDK applications as there is a dependency on the current logical core we are running on. > > > Passing " rte_lcore_to_socket_id(rte_get_master_lcore())" as the socket id to rte_memzone_reserve resolves these issues as the master lcore doesn't change. > > > > > > > The only trouble is that when affinitizing the memory for the NICs to the socket of the master lcore, it gives us no way to correctly configure an app to use NICs connected to two different sockets on the one system. All memory for all NICs will end up on the same socket. Two possible alternative solutions: > > 1) affinitize memory to the socket the NIC is connected to > > 2) add a socket parameter to the API calls to allow the user complete > > control over their memory allocations > > > > Obviously the second one breaks backward compatibility (assume we modify existing API call), but is more powerful. > > > > Thoughts? > > > > /Bruce > > > > > -----Original Message----- > > > From: Ferriter, Cian > > > Sent: Tuesday, January 13, 2015 9:22 AM > > > To: dev@dpdk.org > > > Cc: Ferriter, Cian > > > Subject: [PATCH] lib/librte_ether: change socket_id passed to > > > rte_memzone_reserve > > > > > > Change the socket id that is passed to rte_memzone_reserve from the socket id of current logical core to the socket id of the master_lcore. > > > --- > > > lib/librte_ether/rte_ethdev.c | 2 +- > > > 1 files changed, 1 insertions(+), 1 deletions(-) mode change > > > 100644 => 100755 lib/librte_ether/rte_ethdev.c > > > > > > diff --git a/lib/librte_ether/rte_ethdev.c > > > b/lib/librte_ether/rte_ethdev.c old mode 100644 new mode 100755 > > > index 95f2ceb..835540d > > > --- a/lib/librte_ether/rte_ethdev.c > > > +++ b/lib/librte_ether/rte_ethdev.c > > > @@ -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); > > > } else > > > mz = rte_memzone_lookup(MZ_RTE_ETH_DEV_DATA); > > > if (mz == NULL) > > > -- > > > 1.7.4.1 > > >
diff --git a/lib/librte_ether/rte_ethdev.c b/lib/librte_ether/rte_ethdev.c old mode 100644 new mode 100755 index 95f2ceb..835540d --- a/lib/librte_ether/rte_ethdev.c +++ b/lib/librte_ether/rte_ethdev.c @@ -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); } else mz = rte_memzone_lookup(MZ_RTE_ETH_DEV_DATA); if (mz == NULL)