Re: [Patch] Allocate sparsemem memmap above 4G on X86_64

On 18 May 2007 10:52:57 +0800 Zou Nan hai <[EMAIL PROTECTED]> wrote: > On Fri, 2007-05-18 at 03:32, Andrew Morton wrote: > > On 17 May 2007 10:40:07 +0800 > > Zou Nan hai <[EMAIL PROTECTED]> wrote: > > > > > > > Please always prefer to use static inline functions rather than macros. > > They ar

Re: [Patch] Allocate sparsemem memmap above 4G on X86_64

On Fri, 2007-05-18 at 03:32, Andrew Morton wrote: > On 17 May 2007 10:40:07 +0800 > Zou Nan hai <[EMAIL PROTECTED]> wrote: > > > > Please always prefer to use static inline functions rather than macros. > They are more readable, they are more likely to have comments attached to > them and they p

Re: [Patch] Allocate sparsemem memmap above 4G on X86_64

On 17 May 2007 10:40:07 +0800 Zou Nan hai <[EMAIL PROTECTED]> wrote: > On system with huge amount of physical memory. > VFS cache and memory memmap may eat all available system memory under > 4G, then system may fail to allocated swiotlb bounce buffer. > > There was a fix in arch/x86_64/mm/numa

[Patch] Allocate sparsemem memmap above 4G on X86_64

On system with huge amount of physical memory. VFS cache and memory memmap may eat all available system memory under 4G, then system may fail to allocated swiotlb bounce buffer. There was a fix in arch/x86_64/mm/numa.c, but that fix does not cover sparsemem model. This patch add fix to sparsemem