Thanks for the info! > On Apr 3, 2019, at 6:32 PM, Mohit Verma <moh...@vmware.com> wrote: > > Hi Robert, > > Sorry for the confusion. Our changes are to make byte-addressable persistent > memory support available to Go community. You can find more information about > this technology here: > 1. http://pmem.io/ > 2. > https://www.intel.com/content/www/us/en/architecture-and-technology/optane-dc-persistent-memory.html > > >>> I think the project needs to be distributed as a patch to the Go codebase > >>> - too much to review/maintain for security controls. > We eventually plan to distribute our changes as patches to Go codebase, but > before we do that we wanted to gather feedback here š > > >>> Also, Iāve used pmem for a very long time (I have a bg in retail point of > >>> sale systems where it is very common) and we always had a driver/library > >>> on top of the physical device to multiplex across consumers, and we used > >>> it from Java, and never needed specialized JVM to use it efficiently. > >>> Again, just curious, maybe the use cases have changed. > The recent technological changes have put this technology close to the access > speeds of DRAM, while retaining the persistence property. Quoting from the > blog post in Jerrinās original e-mail: > āAd hoc libraries often provide a difficult programming interface. As memory > management for RAM has increasingly become a part of programming languages, > we believe managing persistent memory should be addressed in the same manner. > And so, our programming model includes changes to Go itself ā. > > There has been a lot of work around this technology in the past few years, > including efforts to change C and Java, and adhoc libraries for C/C++, Java > and Python. These changes are our efforts to make persistent memory > accessible to Go developers. > > Thanks! > Mohit > > From: Robert Engels <reng...@ix.netcom.com> > Date: Wednesday, April 3, 2019 at 4:00 PM > To: Jerrin Shaji George <jshajigeo...@vmware.com> > Cc: "golang-nuts@googlegroups.com" <golang-nuts@googlegroups.com>, Mohit > Verma <moh...@vmware.com>, Pratap Subrahmanyam <pra...@vmware.com>, Rajesh > Venkatasubramanian <vraj...@vmware.com> > Subject: Re: [go-nuts] Persistent memory support for Go > > Also, Iāve used pmem for a very long time (I have a bg in retail point of > sale systems where it is very common) and we always had a driver/library on > top of the physical device to multiplex across consumers, and we used it from > Java, and never needed specialized JVM to use it efficiently. Again, just > curious, maybe the use cases have changed. > > On Apr 3, 2019, at 5:47 PM, Robert Engels <reng...@ix.netcom.com> wrote: > > I think the project needs to be distributed as a patch to the Go codebase - > too much to review/maintain for security controls. > > Also, Iām curious about the Api. In reviewing the example, it looks no > different than any ORM - just flatter -and these donāt need a customized > runtime. > > What would be the advantage of using the Api directly rather than using Redis > (with the support there)? > > No criticism, just not obvious to me. Maybe a link describing the persistent > memory capabilities in detail? > > On Apr 3, 2019, at 5:31 PM, 'Jerrin Shaji George' via golang-nuts > <golang-nuts@googlegroups.com> wrote: > > Hi, > > I am part of a small team at VMware working on projects related to persistent > memory (others in CC). We have recently been working on adding persistent > memory > support to the Go programming language, and I wanted to spread the word about > couple of these projects. > > 1) Go-pmem-transaction > The go-pmem-transaction project introduces a new programming model for > developing applications in Go for persistent memory. It consists of two > packages > - pmem and transaction. > > The pmem package provides methods to initialize persistent memory and an > interface to set and retrieve objects in persistent memory. The transaction > package provides undo and redo transaction logging APIs to support > crash-consistent updates to persistent memory data. > > Project page - https://github.com/vmware/go-pmem-transaction > > 2) Go-pmem > The Go-pmem project adds native persistent memory support to Go. > Some of the features of the persistent memory support added to Go are: > * Support for persistent memory allocations > * Garbage collector now collects objects from persistent heap > and volatile > heap > * Runtime automatically swizzles pointers if the memory > mapping address > changes on an application restart > * The persistent memory heap is dynamically sized and > supports automatic > heap growth depending on memory demand > > Project page - https://github.com/jerrinsg/go-pmem > > The project pages contains links to further documentation. We welcome the > community to try out these projects and send any feedback our way! > > Also see the blog post at > https://blogs.vmware.com/opensource/2019/04/03/persistent-memory-with-go/ > > Thanks, > Jerrin > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout.
-- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
