LSI
Life Storage, Inc.
stock NYSE

Not really sure exactly what AMD is planning to do with MEXT... Your not alone as even this article from The NextPlatform end on this note:
>AMD has not disclosed what it paid to acquire MEXT, and it has not said how it will weave it into its systems – and importantly, whether it will pull a 3D XPoint and not allow it on machines using Intel processors or those running homegrown Arm CPUs. Hopefully, AMD has a more open mind about this than Intel did. We think that is highly likely, in fact.
But...and it's a big BUT... You absolutely need to read the full article, not just the tease out I'll put here. NextPlatfom details out a concise history of the the technology problem and solution that MEXT has addressed and then several key examples of how that matters now and going forward. If you read this, it should give you a nice soap box to stand on while you watch the DRAM feast getting consumed beyond the market window and understand exactly how AMD is about to get ensure their restaurant keeps tables full while only putting a few delicious sticks of RAM on each servers plate.
>“We came up with three problems that, if we could solve them, would change everything,” Smerdon tells The Next Platform. “One, we have got to increase DRAM utilization. That is so obvious. It's what everybody was trying to do CXL, increase DRAM utilization through pooling. There are, however, a lot of ways you can do that. The second problem is that we need no hardware or software changes for memory extension to work. I can go through my career with Ethernet on the motherboard, or working at AMD and LSI, we had fast growing products, and all of them had no software changes. In the ideal world, if you are a software company, you don't want hardware changes, either. And nobody that is focused on the memory problem has had this as a part of their core principles. And the third problem was to bring flash into the memory tier? It was 50X cheaper per bit when we started in 2023, maybe it is 100X times now, with 30X times lower power per bit. This is a great. There's just one little problem: Flash is 500X times slower, and that isn't going to perform well. And we all know that swap sucks, and so we had to crack these problems.”
>The simple answer is to stop putting cold data on DRAM and cram it full of hot data, or data that will need to be hot in a few tens of nanoseconds from now. Pushing pages out from hot to warm to cold onto flash is relatively easy. But the real issue is that data can go from cold to red hot with on instruction running on a CPU, and that happens in a fraction of a nanosecond.
>To do this, MEXT created what it calls Predictive Memory, of course using AI algorithms to watch applications and memory access patterns, to get data from that flash back into DRAM before the applications or the operating system asks for them.
>“We have developed sophisticated machine learning models that have much better prediction accuracy and coverage than what has been done in the past,” explains Waldspurger. “We were inspired by modern AI techniques based on neural networks like LSTMs and LLM transformers, which are actually really excellent at sequence prediction. Instead of predicting tokens in a natural language conversation, we are applying similar ideas to predict sequences of future memory page accesses. And since our AI models run asynchronously, they can also benefit from richer information and context about longer term trends and leverage hardware counters, software events, and application features that aren't considered by traditional approaches. Our AI engine consists of a family of models that work together, and so we have an ensemble that combines both lightweight heuristic predictors and more powerful neural network models. And we are also actively and exploring and having good luck with other AI techniques.”
.......
>Here is the Dell comparison with and without the MEXT extended memory: {chart shown}
>The interesting bit there is not just how much cheaper the server is with flash extended memory, but the fact that Dell is no longer shipping PowerEdge R6725 servers with 3 TB and 6 TB options for main memory. (This was as of February 1.) You can get to 3 TB with a 1:1 ration of flash and DRAM – 1.5 TB each – and you can get to 6 TB effective capacity with a 1:3 ratio with 1.5 TB of DRAM and 4.5 TB of flash.
The article includes a number of different use case examples that show the significant potential of this methodology for memory utilization optimization and ultimately hardware cost savings.
Personally, I don't see where these techniques can't also be Incorporated to vram specific strategies and how AMD moves data between 3D vCache and such as well, although this was not discussed. It's certainly something I'll be looking for as thing progress.

Not really sure exactly what AMD is planning to do with MEXT... Your not alone as even this article from The NextPlatform end on this note:
>AMD has not disclosed what it paid to acquire MEXT, and it has not said how it will weave it into its systems – and importantly, whether it will pull a 3D XPoint and not allow it on machines using Intel processors or those running homegrown Arm CPUs. Hopefully, AMD has a more open mind about this than Intel did. We think that is highly likely, in fact.
But...and it's a big BUT... You absolutely need to read the full article, not just the tease out I'll put here. NextPlatfom details out a concise history of the the technology problem and solution that MEXT has addressed and then several key examples of how that matters now and going forward. If you read this, it should give you a nice soap box to stand on while you watch the DRAM feast getting consumed beyond the market window and understand exactly how AMD is about to get ensure their restaurant keeps tables full while only putting a few delicious sticks of RAM on each servers plate.
>“We came up with three problems that, if we could solve them, would change everything,” Smerdon tells The Next Platform. “One, we have got to increase DRAM utilization. That is so obvious. It's what everybody was trying to do CXL, increase DRAM utilization through pooling. There are, however, a lot of ways you can do that. The second problem is that we need no hardware or software changes for memory extension to work. I can go through my career with Ethernet on the motherboard, or working at AMD and LSI, we had fast growing products, and all of them had no software changes. In the ideal world, if you are a software company, you don't want hardware changes, either. And nobody that is focused on the memory problem has had this as a part of their core principles. And the third problem was to bring flash into the memory tier? It was 50X cheaper per bit when we started in 2023, maybe it is 100X times now, with 30X times lower power per bit. This is a great. There's just one little problem: Flash is 500X times slower, and that isn't going to perform well. And we all know that swap sucks, and so we had to crack these problems.”
>The simple answer is to stop putting cold data on DRAM and cram it full of hot data, or data that will need to be hot in a few tens of nanoseconds from now. Pushing pages out from hot to warm to cold onto flash is relatively easy. But the real issue is that data can go from cold to red hot with on instruction running on a CPU, and that happens in a fraction of a nanosecond.
>To do this, MEXT created what it calls Predictive Memory, of course using AI algorithms to watch applications and memory access patterns, to get data from that flash back into DRAM before the applications or the operating system asks for them.
>“We have developed sophisticated machine learning models that have much better prediction accuracy and coverage than what has been done in the past,” explains Waldspurger. “We were inspired by modern AI techniques based on neural networks like LSTMs and LLM transformers, which are actually really excellent at sequence prediction. Instead of predicting tokens in a natural language conversation, we are applying similar ideas to predict sequences of future memory page accesses. And since our AI models run asynchronously, they can also benefit from richer information and context about longer term trends and leverage hardware counters, software events, and application features that aren't considered by traditional approaches. Our AI engine consists of a family of models that work together, and so we have an ensemble that combines both lightweight heuristic predictors and more powerful neural network models. And we are also actively and exploring and having good luck with other AI techniques.”
.......
>Here is the Dell comparison with and without the MEXT extended memory: {chart shown}
>The interesting bit there is not just how much cheaper the server is with flash extended memory, but the fact that Dell is no longer shipping PowerEdge R6725 servers with 3 TB and 6 TB options for main memory. (This was as of February 1.) You can get to 3 TB with a 1:1 ration of flash and DRAM – 1.5 TB each – and you can get to 6 TB effective capacity with a 1:3 ratio with 1.5 TB of DRAM and 4.5 TB of flash.
The article includes a number of different use case examples that show the significant potential of this methodology for memory utilization optimization and ultimately hardware cost savings.
Personally, I don't see where these techniques can't also be Incorporated to vram specific strategies and how AMD moves data between 3D vCache and such as well, although this was not discussed. It's certainly something I'll be looking for as thing progress.