On Thu, Apr 04, 2013 at 08:17:08AM +0800, Simon Jeons wrote:
> On 03/07/2013 05:50 AM, Cliff Wickman wrote:
>> From: Cliff Wickman
>>
>> Allocating a large number of 1GB hugetlbfs pages at boot takes a
>> very long time.
>>
>> Large system sites would at times like to allocate a very large amount
On Thu, Apr 04, 2013 at 08:17:08AM +0800, Simon Jeons wrote:
On 03/07/2013 05:50 AM, Cliff Wickman wrote:
From: Cliff Wickman c...@sgi.com
Allocating a large number of 1GB hugetlbfs pages at boot takes a
very long time.
Large system sites would at times like to allocate a very large amount
On 03/07/2013 05:50 AM, Cliff Wickman wrote:
From: Cliff Wickman
Allocating a large number of 1GB hugetlbfs pages at boot takes a
very long time.
Large system sites would at times like to allocate a very large amount of
memory as 1GB pages. They would put this on the kernel boot line:
On 03/07/2013 05:50 AM, Cliff Wickman wrote:
From: Cliff Wickman c...@sgi.com
Allocating a large number of 1GB hugetlbfs pages at boot takes a
very long time.
Large system sites would at times like to allocate a very large amount of
memory as 1GB pages. They would put this on the kernel boot
On Wed 06-03-13 15:50:20, Cliff Wickman wrote:
[...]
> I propose passing a flag to the early allocator to indicate that no zeroing
> of a page should be done. The 'no zeroing' flag would have to be passed
> down this code path:
>
> hugetlb_hstate_alloc_pages
> alloc_bootmem_huge_page
>
On Wed 06-03-13 15:50:20, Cliff Wickman wrote:
[...]
I propose passing a flag to the early allocator to indicate that no zeroing
of a page should be done. The 'no zeroing' flag would have to be passed
down this code path:
hugetlb_hstate_alloc_pages
alloc_bootmem_huge_page
On Sun, Mar 10, 2013 at 01:55:10PM +0800, Hillf Danton wrote:
> On Thu, Mar 7, 2013 at 5:50 AM, Cliff Wickman wrote:
> > From: Cliff Wickman
> >
> > Allocating a large number of 1GB hugetlbfs pages at boot takes a
> > very long time.
> >
> > Large system sites would at times like to allocate a
On Sun, Mar 10, 2013 at 01:55:10PM +0800, Hillf Danton wrote:
On Thu, Mar 7, 2013 at 5:50 AM, Cliff Wickman c...@sgi.com wrote:
From: Cliff Wickman c...@sgi.com
Allocating a large number of 1GB hugetlbfs pages at boot takes a
very long time.
Large system sites would at times like to
On Thu, Mar 7, 2013 at 5:50 AM, Cliff Wickman wrote:
> From: Cliff Wickman
>
> Allocating a large number of 1GB hugetlbfs pages at boot takes a
> very long time.
>
> Large system sites would at times like to allocate a very large amount of
> memory as 1GB pages. They would put this on the
On Thu, Mar 7, 2013 at 5:50 AM, Cliff Wickman c...@sgi.com wrote:
From: Cliff Wickman c...@sgi.com
Allocating a large number of 1GB hugetlbfs pages at boot takes a
very long time.
Large system sites would at times like to allocate a very large amount of
memory as 1GB pages. They would put
From: Cliff Wickman
Allocating a large number of 1GB hugetlbfs pages at boot takes a
very long time.
Large system sites would at times like to allocate a very large amount of
memory as 1GB pages. They would put this on the kernel boot line:
default_hugepagesz=1G hugepagesz=1G
From: Cliff Wickman c...@sgi.com
Allocating a large number of 1GB hugetlbfs pages at boot takes a
very long time.
Large system sites would at times like to allocate a very large amount of
memory as 1GB pages. They would put this on the kernel boot line:
default_hugepagesz=1G hugepagesz=1G
12 matches
Mail list logo
