On Tue, 4 Nov 2014, Daniel J Blueman wrote:
> On 11/04/2014 07:36 AM, Thomas Gleixner wrote:
> > On Tue, 4 Nov 2014, Daniel J Blueman wrote:
> > > > > @@ -1247,9 +1246,9 @@ static unsigned long
> > > > > probe_memory_block_size(void)
> > > > > /* start from 2g */
> > > > > unsigned
On 11/04/2014 07:36 AM, Thomas Gleixner wrote:
On Tue, 4 Nov 2014, Daniel J Blueman wrote:
On 11/04/2014 03:38 AM, Thomas Gleixner wrote:
On Sun, 2 Nov 2014, Daniel J Blueman wrote:
On larger x64-64 systems, use a 2GB memory block size to reduce sysfs
entry creation time by 16x. Large is
On Tue, 4 Nov 2014, Daniel J Blueman wrote:
> On 11/04/2014 03:38 AM, Thomas Gleixner wrote:
> > On Sun, 2 Nov 2014, Daniel J Blueman wrote:
> >
> > > On larger x64-64 systems, use a 2GB memory block size to reduce sysfs
> > > entry creation time by 16x. Large is defined as 64GB or more memory.
On 11/04/2014 03:38 AM, Thomas Gleixner wrote:
On Sun, 2 Nov 2014, Daniel J Blueman wrote:
On larger x64-64 systems, use a 2GB memory block size to reduce sysfs
entry creation time by 16x. Large is defined as 64GB or more memory.
This changelog sucks.
It neither tells which sysfs entries
On Sun, 2 Nov 2014, Daniel J Blueman wrote:
> On larger x64-64 systems, use a 2GB memory block size to reduce sysfs
> entry creation time by 16x. Large is defined as 64GB or more memory.
This changelog sucks.
It neither tells which sysfs entries are meant nor does it explain
what the actual
On Sun, 2 Nov 2014, Daniel J Blueman wrote:
On larger x64-64 systems, use a 2GB memory block size to reduce sysfs
entry creation time by 16x. Large is defined as 64GB or more memory.
This changelog sucks.
It neither tells which sysfs entries are meant nor does it explain
what the actual
On 11/04/2014 03:38 AM, Thomas Gleixner wrote:
On Sun, 2 Nov 2014, Daniel J Blueman wrote:
On larger x64-64 systems, use a 2GB memory block size to reduce sysfs
entry creation time by 16x. Large is defined as 64GB or more memory.
This changelog sucks.
It neither tells which sysfs entries
On Tue, 4 Nov 2014, Daniel J Blueman wrote:
On 11/04/2014 03:38 AM, Thomas Gleixner wrote:
On Sun, 2 Nov 2014, Daniel J Blueman wrote:
On larger x64-64 systems, use a 2GB memory block size to reduce sysfs
entry creation time by 16x. Large is defined as 64GB or more memory.
This
On 11/04/2014 07:36 AM, Thomas Gleixner wrote:
On Tue, 4 Nov 2014, Daniel J Blueman wrote:
On 11/04/2014 03:38 AM, Thomas Gleixner wrote:
On Sun, 2 Nov 2014, Daniel J Blueman wrote:
On larger x64-64 systems, use a 2GB memory block size to reduce sysfs
entry creation time by 16x. Large is
On Tue, 4 Nov 2014, Daniel J Blueman wrote:
On 11/04/2014 07:36 AM, Thomas Gleixner wrote:
On Tue, 4 Nov 2014, Daniel J Blueman wrote:
@@ -1247,9 +1246,9 @@ static unsigned long
probe_memory_block_size(void)
/* start from 2g */
unsigned long bz = 1UL31;
On larger x64-64 systems, use a 2GB memory block size to reduce sysfs
entry creation time by 16x. Large is defined as 64GB or more memory.
Signed-off-by: Daniel J Blueman
---
arch/x86/mm/init_64.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/arch/x86/mm/init_64.c
On larger x64-64 systems, use a 2GB memory block size to reduce sysfs
entry creation time by 16x. Large is defined as 64GB or more memory.
Signed-off-by: Daniel J Blueman dan...@numascale.com
---
arch/x86/mm/init_64.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git
12 matches
Mail list logo
