Date: Sat, 25 Mar 2017 14:50:38 +0300 From: Slawa Olhovchenkov <slw@zxy.spb.ru> To: Ravi Pokala <rpokala@mac.com> Cc: freebsd-arch@freebsd.org Subject: Re: NVDIMM status report Message-ID: <20170325115038.GJ86500@zxy.spb.ru> In-Reply-To: <A7AB0219-990E-4C73-924A-874E73EFED53@mac.com> References: <A7AB0219-990E-4C73-924A-874E73EFED53@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 24, 2017 at 02:40:19PM -0700, Ravi Pokala wrote: > 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, Thanks, very interesting! What limited to extending kernel API (destroy sub-map, drop MAX_KMAP limitations)?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170325115038.GJ86500>