On Mon, Jun 15, 2015 at 05:47:27PM +0900, Kamezawa Hiroyuki wrote: > So, there are 3 ideas. > > (1) kernel only from MIRROR / user only from MOVABLE (Tony) > (2) kernel only from MIRROR / user from MOVABLE + MIRROR(ASAP) (AKPM suggested) > This makes use of the fact MOVABLE memory is reclaimable but Tony pointed out > the memory reclaim can be critical for GFP_ATOMIC. > (3) kernel only from MIRROR / user from MOVABLE, special user from MIRROR (Xishi) > > 2 Implementation ideas. > - creating ZONE > - creating new alloation attribute > > I don't convince whether we need some new structure in mm. Isn't it good to use > ZONE_MOVABLE for not-mirrored memory ? > Then, disable fallback from ZONE_MOVABLE -> ZONE_NORMAL for (1) and (3) We might need to rename it ... right now the memory hotplug people use ZONE_MOVABLE to indicate regions of physical memory that can be removed from the system. I'm wondering whether people will want systems that have both removable and mirrored areas? Then we have four attribute combinations: mirror=no removable=no - prefer to use for user, could use for kernel if we run out of mirror mirror=no removable=yes - can only be used for user (kernel allocation makes it not-removable) mirror=yes removable=no - use for kernel, possibly for special users if we define some interface mirror=yes removable=yes - must not use for kernel ... would have to give to user ... seems like a bad idea to configure a system this way -Tony -- 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>