NVDIMM status report

[Ravi Pokala]

Greetings,

At the 2016-11 Dev and Vendor Summit, I noted that Panasas (my employer) has been working on NVDIMMs. Since then, several people have contacted me for more information. Please accept my apologies for the long delay in responding.

This turned out to be a much larger explanation than I originally thought. Rather than send a wall of text in email, I moved it into file and uploaded it to the server; interested parties can view it here:

https://people.freebsd.org/~rpokala/2017-03-24.nvdimm.txt

I'll do my best to answer questions and/or make the proper introductions with the people inside Panasas who can.

Thanks for your interest,

Ravi (rpokala@)

[Slawa Olhovchenkov]

Post by Ravi Pokala
Greetings,
At the 2016-11 Dev and Vendor Summit, I noted that Panasas (my employer) has been working on NVDIMMs. Since then, several people have contacted me for more information. Please accept my apologies for the long delay in responding.
https://people.freebsd.org/~rpokala/2017-03-24.nvdimm.txt
I'll do my best to answer questions and/or make the proper introductions with the people inside Panasas who can.
Thanks for your interest,

Thanks, very interesting!
What limited to extending kernel API (destroy sub-map, drop MAX_KMAP
limitations)?