lkml.org 
[lkml]   [2012]   [Jan]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: x86-64: memset()/memcpy() not fully standards compliant
>>> On 06.01.12 at 11:37, Andi Kleen <andi@firstfloor.org> wrote:
>> > You would slow a critical fast path operation down for something
>> > that never happens?!?
>>
>> It does happen, just (so far) not in-tree. It's a latent problem that's
>> just waiting for someone else to run into. Apart from large bootmem
>> allocations (where not even the latency of the memory clearing
>
> Modern kernels are bootmem less.

It's not the traditional bootmem implementation anymore, but
alloc_bootmem() et al still exist, and still clear the allocated memory
(in __alloc_memory_core_early()). So there is a code path that can
validly be used (and it is this code path that is presenting one of the
problems with the non-pv-ops Xen kernels, as they're using flatmem
rather than sparsemem since their physical address space is always
fully continuous).

Jan



\
 
 \ /
  Last update: 2012-01-06 11:51    [W:0.072 / U:0.664 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site