1 On Wed, Oct 16, 2019 at 1:05 PM Dave Hansen <dave.hansen@xxxxxxxxx> wrote: > > The memory hierarchy is getting more complicated and the kernel is > playing an increasing role in managing the different tiers. A few > different groups of folks described "migration" optimizations they were > doing in this area at LSF/MM earlier this year. One of the questions > folks asked was why autonuma wasn't being used. > > At Intel, the primary new tier that we're looking at is persistent > memory (PMEM). We'd like to be able to use "persistent memory" > *without* using its persistence properties, treating it as slightly > slower DRAM. Keith Busch has some patches to use NUMA migration to > automatically migrate DRAM->PMEM instead of discarding it near the end > of the reclaim process. Huang Ying has some patches which use a > modified autonuma to migrate frequently-used data *back* from PMEM->DRAM. > > We've tried to do this all generically so that it is not tied to > persistent memory and can be applied to any memory types in lots of > topologies. > > We've been running this code in various forms for the past few months, > comparing it to pure DRAM and hardware-based caching. The initial > results are encouraging and we thought others might want to take a look > at the code or run their own experiments. We're expecting to post the > individual patches soon. But, until then, the code is available here: > > https://git.kernel.org/pub/scm/linux/kernel/git/vishal/tiering.git > > and is tagged with "tiering-0.2", aka. d8e31e81b1dca9. Hi Dave, Thanks for sharing this git link and information on your approach. This interesting, and lines up somewhat with the approach Google has been investigating. As we discussed at LSF/MM[1] and Linux Plumbers[2], we're working on an approach which integrates with our proactive reclaim work, with a similar attitude to PMEM (use it as "slightly slower" DRAM, ignoring its persistence). The prototype we have has a similar basic structure to what you're doing here and Yang Shi's patchset from March[3] (separate NUMA nodes for PMEM), but relies on a fair amount of kernel changes to control allocations from the NUMA nodes, and uses a similar "is_far" NUMA flag to Yang Shi's approach. We're working on redesigning to reduce the scope of kernel changes and to remove the "is_far" special handling; we still haven't refined down to a final approach, but one basic part we want to keep from the prototype is proactively pushing PMEM data back to DRAM when we've noticed it's in use. If we look at a two-socket system: A: DRAM & CPU node for socket 0 B: PMEM node for socket 0 C: DRAM & CPU node for socket 1 D: PMEM node for socket 1 instead of the unidirectional approach your patches go for: A is marked as "in reclaim, push pages to" B C is marked as "in reclaim, push pages to" D B & D have no markings we would have a bidirectional attachment: A is marked "move cold pages to" B B is marked "move hot pages to" A C is marked "move cold pages to" D D is marked "move hot pages to" C By using autonuma for moving PMEM pages back to DRAM, you avoid needing the B->A & D->C links, at the cost of migrating the pages back synchronously at pagefault time (assuming my understanding of how autonuma works is accurate). Our approach still lets you have multiple levels of hierarchy for a given socket (you could imaging an "E" node with the same relation to "B" as "B" has to "A"), but doesn't make it easy to represent (say) an "E" which was equally close to all sockets (which I could imagine for something like remote memory on GenZ or what-have-you), since there wouldn't be a single back link; there would need to be something like your autonuma support to achieve that. Does that make sense? Thanks, - Jonathan [1] Shakeel's talk, I can't find a link at the moment. The basic kstaled/kreclaimd approach we built upon is talked about in https://blog.acolyer.org/2019/05/22/sw-far-memory/ and the linked ASPLOS paper [2] https://linuxplumbersconf.org/event/4/contributions/561/; slides at https://linuxplumbersconf.org/event/4/contributions/561/attachments/363/596/Persistent_Memory_as_Memory.pdf [3] https://lkml.org/lkml/2019/3/23/10
