On 2015/5/19 12:48, Tony Luck wrote:
> On Mon, May 18, 2015 at 8:01 PM, Xishi Qiu wrote:
>> In part2, does it means the memory allocated from kernel should use mirrored
>> memory?
>
> Yes. I want to use mirrored memory for all (or as many as
> possible) kernel allocations.
>
>> I have heard
On 2015/5/19 12:48, Tony Luck wrote:
On Mon, May 18, 2015 at 8:01 PM, Xishi Qiu qiuxi...@huawei.com wrote:
In part2, does it means the memory allocated from kernel should use mirrored
memory?
Yes. I want to use mirrored memory for all (or as many as
possible) kernel allocations.
I have
On Mon, May 18, 2015 at 8:01 PM, Xishi Qiu wrote:
> In part2, does it means the memory allocated from kernel should use mirrored
> memory?
Yes. I want to use mirrored memory for all (or as many as
possible) kernel allocations.
> I have heard of this feature(address range mirroring) before, and
On 2015/5/9 0:44, Tony Luck wrote:
> Some high end Intel Xeon systems report uncorrectable memory errors
> as a recoverable machine check. Linux has included code for some time
> to process these and just signal the affected processes (or even
> recover completely if the error was in a read only
On 2015/5/9 0:44, Tony Luck wrote:
Some high end Intel Xeon systems report uncorrectable memory errors
as a recoverable machine check. Linux has included code for some time
to process these and just signal the affected processes (or even
recover completely if the error was in a read only page
On Mon, May 18, 2015 at 8:01 PM, Xishi Qiu qiuxi...@huawei.com wrote:
In part2, does it means the memory allocated from kernel should use mirrored
memory?
Yes. I want to use mirrored memory for all (or as many as
possible) kernel allocations.
I have heard of this feature(address range
On Fri, May 8, 2015 at 1:49 PM, Andrew Morton wrote:
> What I mean is: allow userspace to consume ZONE_MIRROR memory because
> we can snatch it back if it is needed for kernel memory.
For suitable interpretations of "snatch it back" ... if there is none
free in a GFP_NOWAIT request, then we are
On Fri, 8 May 2015 13:38:52 -0700 Tony Luck wrote:
> > Will surplus ZONE_MIRROR memory be available for regular old movable
> > allocations?
> ZONE_MIRROR and ZONE_MOVABLE are pretty much opposites. We
> only want kernel allocations in mirror memory, and we can't allow any
> kernel allocations
On Fri, May 8, 2015 at 1:03 PM, Andrew Morton wrote:
> Looks good to me. What happens to these patches while ZONE_MIRROR is
> being worked on?
I think these patches can go into the kernel now while I figure
out the next phase - there is some value in just this part. We'll
have all memory <4GB
On Fri, 8 May 2015 09:44:21 -0700 Tony Luck wrote:
> Some high end Intel Xeon systems report uncorrectable memory errors
> as a recoverable machine check. Linux has included code for some time
> to process these and just signal the affected processes (or even
> recover completely if the error
Some high end Intel Xeon systems report uncorrectable memory errors
as a recoverable machine check. Linux has included code for some time
to process these and just signal the affected processes (or even
recover completely if the error was in a read only page that can be
replaced by reading from
Some high end Intel Xeon systems report uncorrectable memory errors
as a recoverable machine check. Linux has included code for some time
to process these and just signal the affected processes (or even
recover completely if the error was in a read only page that can be
replaced by reading from
On Fri, 8 May 2015 13:38:52 -0700 Tony Luck tony.l...@gmail.com wrote:
Will surplus ZONE_MIRROR memory be available for regular old movable
allocations?
ZONE_MIRROR and ZONE_MOVABLE are pretty much opposites. We
only want kernel allocations in mirror memory, and we can't allow any
kernel
On Fri, 8 May 2015 09:44:21 -0700 Tony Luck tony.l...@intel.com wrote:
Some high end Intel Xeon systems report uncorrectable memory errors
as a recoverable machine check. Linux has included code for some time
to process these and just signal the affected processes (or even
recover completely
On Fri, May 8, 2015 at 1:49 PM, Andrew Morton a...@linux-foundation.org wrote:
What I mean is: allow userspace to consume ZONE_MIRROR memory because
we can snatch it back if it is needed for kernel memory.
For suitable interpretations of snatch it back ... if there is none
free in a GFP_NOWAIT
On Fri, May 8, 2015 at 1:03 PM, Andrew Morton a...@linux-foundation.org wrote:
Looks good to me. What happens to these patches while ZONE_MIRROR is
being worked on?
I think these patches can go into the kernel now while I figure
out the next phase - there is some value in just this part. We'll
16 matches
Mail list logo
