Re: [edk2] [Patch] MdeModulePkg: DxeCore MemoryPool Algorithm Update

2016-04-27 Thread Kinney, Michael D
With that update, Reviewed-by: Michael Kinney Mike From: Gao, Liming Sent: Wednesday, April 27, 2016 5:51 PM To: Ard Biesheuvel Cc: edk2-devel-01 ; Kinney, Michael D Subject: RE: [Patch] MdeModulePkg: DxeCore MemoryPool Algorithm Update Good catch. I will update it. From: Ard Biesheuvel

Re: [edk2] [Patch] MdeModulePkg: DxeCore MemoryPool Algorithm Update

2016-04-27 Thread Gao, Liming
Good catch. I will update it. From: Ard Biesheuvel [mailto:ard.biesheu...@linaro.org] Sent: Thursday, April 28, 2016 12:05 AM To: Gao, Liming Cc: edk2-devel-01 ; Kinney, Michael D Subject: Re: [Patch] MdeModulePkg: DxeCore MemoryPool Algorithm Update On 27 April 2016 at 08:40, Liming Gao wrote

Re: [edk2] [Patch] MdeModulePkg: DxeCore MemoryPool Algorithm Update

2016-04-27 Thread Ard Biesheuvel
On 27 April 2016 at 08:40, Liming Gao wrote: > Use 128 bytes as the start size region to be same to previous one. > > 64 bytes is small as the first range. On X64 arch, POOL_OVERHEAD > takes 40 bytes, the pool data less than 24 bytes can be fit into > it. But, the real allocation is few that can't

[edk2] [Patch] MdeModulePkg: DxeCore MemoryPool Algorithm Update

2016-04-26 Thread Liming Gao
Use 128 bytes as the start size region to be same to previous one. 64 bytes is small as the first range. On X64 arch, POOL_OVERHEAD takes 40 bytes, the pool data less than 24 bytes can be fit into it. But, the real allocation is few that can't reduce its free pool link list. And, the second range