On 2015/12/10 13:37, Izumi, Taku wrote: > Dear Tony, Xishi, > >>>> How about add some comment, if mirrored memroy is too small, then the >>>> normal zone is small, so it may be oom. >>>> The mirrored memory is at least 1/64 of whole memory, because struct >>>> pages usually take 64 bytes per page. >>> >>> 1/64th is the absolute lower bound (for the page structures as you say). I >>> expect people will need to configure 10% or more to run any real workloads. > >>> >>> I made the memblock boot time allocator fall back to non-mirrored memory >>> if mirrored memory ran out. What happens in the run time allocator if the >>> non-movable zones run out of pages? Will we allocate kernel pages from movable >>> memory? >>> >> >> As I know, the kernel pages will not allocated from movable zone. > > Yes, kernel pages are not allocated from ZONE_MOVABLE. > > In this case administrator must review and reconfigure the mirror ratio via > "MirrorRequest" EFI variable. > > Sincerely, > Taku Izumi > Hi Taku, Whether it is possible that we rewrite the fallback function in buddy system when zone_movable and mirrored_kernelcore are both enabled? It seems something like that we add a new zone but the name is zone_movable, not zone_mirror. And the prerequisite is that we won't enable these two features(movable memory and mirrored memory) at the same time. Thus we can reuse the code of movable zone. Thanks, Xishi Qiu >> >>> -- >>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in >>> the body of a message to majordomo@xxxxxxxxxxxxxxx >>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>> Please read the FAQ at http://www.tux.org/lkml/ >>> >>> . >>> >> >> > > > . > -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>