"Chao Zhu" wrote on 11/09/2017 04:08:36 AM:
> From: "Chao Zhu"
> To: "'Jonas Pfefferle1'"
> Cc: "'Burakov, Anatoly'" ,
> ,
> Date: 11/09/2017 04:08 AM
> Subject: RE: [dpdk-dev] Huge mapping secondary process linux
From: Jonas Pfefferle1 [mailto:j...@zurich.ibm.com]
Sent: 2017年11月7日 18:16
To: Chao Zhu
Cc: 'Burakov, Anatoly' ; bruce.richard...@intel.com;
dev@dpdk.org
Subject: RE: [dpdk-dev] Huge mapping secondary process linux
"Chao Zhu" mailto:chao...@linux.vnet.ibm.com>
"Chao Zhu" wrote on 11/07/2017 09:25:26 AM:
> From: "Chao Zhu"
> To: "'Jonas Pfefferle1'" , "'Burakov, Anatoly'"
>
> Cc: ,
> Date: 11/07/2017 11:00 AM
> Subject: RE: [dpdk-dev] Huge mapping secondary process linux
&
From: Jonas Pfefferle1 [mailto:j...@zurich.ibm.com]
Sent: 2017年10月28日 3:23
To: Burakov, Anatoly
Cc: bruce.richard...@intel.com; chao...@linux.vnet.ibm.com; dev@dpdk.org
Subject: Re: [dpdk-dev] Huge mapping secondary process linux
"Burakov, Anatoly" < <mailto:anatoly.b
"Burakov, Anatoly" wrote on 27/10/2017
18:00:27:
> From: "Burakov, Anatoly"
> To: Jonas Pfefferle1
> Cc: bruce.richard...@intel.com, chao...@linux.vnet.ibm.com, dev@dpdk.org
> Date: 27/10/2017 18:00
> Subject: Re: [dpdk-dev] Huge mapping secondary proc
, dev@dpdk.org
> Cc: chao...@linux.vnet.ibm.com, bruce.richard...@intel.com
> Date: 10/27/2017 04:06 PM
> Subject: Re: [dpdk-dev] Huge mapping secondary process linux
...
> >
> hi Jonas,
>
> MAP_FIXED is not used because it's dangerous, it unmaps anything
that is
> already mappe
2017
> > > 04:06:44 PM:
> > >
> > > > From: "Burakov, Anatoly"
> > > > To: Jonas Pfefferle1 , dev@dpdk.org
> > > > Cc: chao...@linux.vnet.ibm.com, bruce.richard...@intel.com
> > > > Date: 10/27/2017 04:06 PM
> &
d...@intel.com
> Date: 10/27/2017 04:06 PM
> Subject: Re: [dpdk-dev] Huge mapping secondary process linux
...
> >
> hi Jonas,
>
> MAP_FIXED is not used because it's dangerous, it unmaps anything
that is
> already mapped into that space. We would rather kn
"dev" wrote on 10/27/2017 04:58:01 PM:
> From: "Jonas Pfefferle1"
> To: "Burakov, Anatoly"
> Cc: bruce.richard...@intel.com, chao...@linux.vnet.ibm.com, dev@dpdk.org
> Date: 10/27/2017 04:58 PM
> Subject: Re: [dpdk-dev] Huge mapping secondary p
"Burakov, Anatoly" wrote on 10/27/2017 04:44:52
PM:
> From: "Burakov, Anatoly"
> To: Jonas Pfefferle1
> Cc: bruce.richard...@intel.com, chao...@linux.vnet.ibm.com, dev@dpdk.org
> Date: 10/27/2017 04:45 PM
> Subject: Re: [dpdk-dev] Huge mapping secondary pro
> Subject: Re: [dpdk-dev] Huge mapping secondary process linux
>
> On 27-Oct-17 1:43 PM, Jonas Pfefferle1 wrote:
> >
> >
> > Hi @all,
> >
> > I'm trying to make sense of the hugepage memory mappings in
> > librte_eal/linuxapp/eal/eal_m
"Burakov, Anatoly" wrote on 10/27/2017 04:06:44
PM:
> From: "Burakov, Anatoly"
> To: Jonas Pfefferle1 , dev@dpdk.org
> Cc: chao...@linux.vnet.ibm.com, bruce.richard...@intel.com
> Date: 10/27/2017 04:06 PM
> Subject: Re: [dpdk-dev] Huge mapping secondary pro
On 27-Oct-17 1:43 PM, Jonas Pfefferle1 wrote:
Hi @all,
I'm trying to make sense of the hugepage memory mappings in
librte_eal/linuxapp/eal/eal_memory.c:
* In rte_eal_hugepage_attach (line 1347) when we try to do a private
mapping on /dev/zero (line 1393) why do we not use MAP_FIXED if we need
Hi @all,
I'm trying to make sense of the hugepage memory mappings in
librte_eal/linuxapp/eal/eal_memory.c:
* In rte_eal_hugepage_attach (line 1347) when we try to do a private
mapping on /dev/zero (line 1393) why do we not use MAP_FIXED if we need the
addresses to be identical with the primary p
14 matches
Mail list logo
