Podcasts about persistent memory

We're building a completely hidden Linux OS inside an existing system—with no trace left behind.Sponsored By:Tailscale: Tailscale is a programmable networking software that is private and secure by default - get it free on up to 100 devices!Kolide: Kolide is a device trust solution for companies with Okta, and they ensure that if a device isn't trusted and secure, it can't log into your cloud apps.Support LINUX UnpluggedLinks:

NOTES This episode of BSDNow is brought to you by Tarsnap (https://www.tarsnap.com/bsdnow) and the BSDNow Patreon (https://www.patreon.com/bsdnow) Headlines FreeBSD Quarterly Status Report First Quarter 2022 (https://www.freebsd.org/status/report-2022-01-2022-03/) Installing Nginx on OpenBSD 7.1 (https://unixcop.com/installing-nginx-on-openbsd-7-1/) News Roundup Live Webinar: Open-source Virtualization: Getting started with bhyve (https://klarasystems.com/webinars/live-sessions-singup/webinar-open-source-virtualization-getting-started-with-bhyve/) Hosted by Jim Salter and Allan Jude Live July 12th at 13:00 ET Available on-demand a few days later Persistent Memory Allocation (https://queue.acm.org/detail.cfm?id=3534855) Colorize your BSD shell (https://forums.FreeBSD.org/threads/colorize-your-bsd-shell.85458/) How to Install cgit With Gitolite and Nginx on FreeBSD 13 (https://herrbischoff.com/2021/10/how-to-install-cgit-with-gitolite-and-nginx-on-freebsd-13) EuroBSDCon 2022 (Austria) Program announced (https://2022.eurobsdcon.org/program/) Come to Austria and learn about the latest happenings in the BSDs 2 days of tutorials, and 2 days of 3 concurrent tracks of talks Registration is open now. See you there! *** Tarsnap This weeks episode of BSDNow was sponsored by our friends at Tarsnap, the only secure online backup you can trust your data to. Even paranoids need backups. Feedback/Questions Brad - Drive question (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/461/feedback/Brad%20-%20Drive%20question.md) Carl - Wiring question (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/461/feedback/Carl%20-%20Wiring%20question.md) Jon - Jails question (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/461/feedback/Jon%20-%20Jails%20question.md) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) ***

Five years ago, Intel came up with a new chip, a silicon chip, to store data. With this chip, users can expand the memory component of their server larger than ever before. Shelby Skrhak speaks with Ken Lloyd, Director of US SLED at Intel, about: - How Optane splits the difference between NAND and DRAM - Common uses for Optane - How Optane works with virtualized workloads - Why it's great for public sector and education For more information, contact Andrew Calabrese (andrew.calabrese@ingrammicro.com) or visit Intel Optane Persistent Memory. To join the discussion, follow us on Twitter @IngramTechSol #B2BTechTalk Listen to this episode and more like it by subscribing to B2B Tech Talk on Spotify, Apple Podcasts, or Stitcher. Or, tune in on our website.

EP191 - Persistent Memory Database   Entre no nosso canal do Telegram para receber conteúdos Exclusivos sobre Banco de dados Oracle:   https://t.me/joinchat/AAAAAEb7ufK-90djaVuR4Q

EP192 - Persistent Memory Database   Entre no nosso canal do Telegram para receber conteúdos Exclusivos sobre Banco de dados Oracle:   https://t.me/joinchat/AAAAAEb7ufK-90djaVuR4Q

Darren Pulsipher, Chief Solution Architect, Intel, talks to Charles Fan, CEO of MemVerge, about use cases with their software that utilizes Intel's Optane persistent memory in an innovative way, removing the bottleneck between memory and storage. Blog: Video: https://youtu.be/nTy8yXORkOw

It's Not Always Alzheimer's Persistent memory lapses that begin to interfere with your life should not be ignored. A head injury can result in long-lasting motor, cognitive, communicative, and psychosocial disabilities that range from mild to severe. Susan Cullen, a speech-language pathologist with the IACH Department of Behavioral Health, is uniquely trained to manage cognitive-communication disorders. While some individuals with severe injuries may have forgotten parts of their past it is much more common to have trouble remembering recent events, experience a decline of attention skills and an inability to follow instructions

Link to bioRxiv paper: http://biorxiv.org/cgi/content/short/2020.08.31.276147v1?rss=1 Authors: Kalle Kossio, F. Y., Goedeke, S., Klos, C., Memmesheimer, R.-M. Abstract: Change is ubiquitous in living beings. In particular, the connectome and neural representations can change. Nevertheless behaviors and memories often persist over long times. In a standard model, memories are represented by assemblies of strongly interconnected neurons. For faithful storage these assemblies are assumed to consist of the same neurons over time. Here we propose a contrasting memory model with complete temporal remodeling of assemblies, based on experimentally observed changes of connections and neural representations. The assemblies drift freely as spontaneous synaptic turnover or random activity induce neuron exchange. The gradual exchange allows activity dependent and homeostatic plasticity to conserve the representational structure and keep inputs, outputs and assemblies consistent. This leads to persistent memory. Our findings explain recent experimental results on the temporal evolution of fear memory representations and suggest that memory systems need to be understood in their completeness as individual parts may constantly change. Copy rights belong to original authors. Visit the link for more info

This week the team double down on the topics of in-memory computing and persistent memory. Chris and Martin talk to Charles Fan, CEO at MemVerge about Big Memory and using persistent memory technology (specifically Optane) to supplement system DRAM. DRAM is expensive and as capacities scale linearly, the price of memory increases exponentially. Systems are […] The post #171 – Exploiting Persistent Memory with MemVerge appeared first on Storage Unpacked Podcast.

Intel started showing off persistent memory in 2018, before launching formally in April of… The post #60: Kristie Mann, Intel Persistent Memory appeared first on StorageReview.com.

In this special episode of the Futurum Tech Podcast Interview Series, Daniel Newman welcomes back Intel's Kristie Mann, Sr. Director of Product Management for Intel's Optane DC Persistent Memory products. In the first part of the interview, Daniel and Kristie explored the impact memory has had on businesses. In this episode, the two dig a bit deeper into Optane technology to understand how it works in the real world technological ecosystem. Thank you to Intel for sponsoring this edition of Futurum Tech Podcast. INFORMATION: This Futurum Podcast features Daniel Newman (@danielnewmanUV). If you haven't already, please subscribe to our show on iTunes or SoundCloud. For inquiries or more information on the show, email the team at podcast@futurumresearch.com or follow @FuturumPodcast on Twitter. To learn more about Futurum Research please visit www.futurumresearch.com. DISCLOSURE: Futurum Research is a research and analysis provider, not an investment advisor. The Futurum Tech Podcast (and all related written notes and materials) is a newsletter/podcast intended for entertainment and informational purposes only. Futurum Research does not provide personalized investment advice and no investment advice is offered or implied by this podcast. ###

In this special edition episode of the Futurum Tech Podcast Interview Series, Daniel Newman welcomes Kristie Mann, Sr. Director of Product Management for Intel's Optane DC persistent memory products. Over the course of the last year, Futurum Research and Intel partnered to do some extensive research around memory in compute and the future of memory and the data center. Our society has come to depend on data consumption and creation for almost all aspects of our lives — and our data architecture needs to keep up. Intel's Optane, in the works for 10 years, was launched eight months ago. It merges the best of storage and memory to improve data accessibility and performance in today's data centers. Thank you to Intel for sponsoring this edition of Futurum Tech Podcast. INFORMATION: This Futurum Podcast features Daniel Newman (@danielnewmanUV). If you haven't already, please subscribe to our show on iTunes or SoundCloud. For inquiries or more information on the show, email the team at podcast@futurumresearch.com or follow @FuturumPodcast on Twitter. To learn more about Futurum Research please visit www.futurumresearch.com. DISCLOSURE: Futurum Research is a research and analysis provider, not an investment advisor. The Futurum Tech Podcast (and all related written notes and materials) is a newsletter/podcast intended for entertainment and informational purposes only. Futurum Research does not provide personalized investment advice and no investment advice is offered or implied by this podcast. ###

Dr. Jishen Zhao

This week on the podcast, we talk to Enterprise Solutions Architect at Intel, Ken LeTourneau and NetApp’s MaxDATA TME Chris Gebhardt to discuss SQL Server on persistent memory and where MaxDATA projects to fit in to the solution.

Intel's new Persistent Memory technology has three modes of operation. One as an extension of your current memory. Imagine extending your server with 9TBytes of Memory. The second is called AppDirect mode where you can use the Persistent Memory as a persistent segment of memory or as a high-speed SSD. The third mode is called mix mode. In this mode, a percentage of the persistent memory is used for AppDirect and the other to extend your standard DDR4 Memory. When exploring this new technology, I realized that I could take the persistent memory and use it as a high-speed SSD. If I did that could I increase the throughput of my ElasticSearch Server? So I set up a test suite to try this out.

Joaquin Ruiz, Senior Director of Product Management at NetApp*, joins Chip Chat to talk about facilitating data access and analysis with Intel® Optane™ DC persistent memory. Ruiz is responsible for product management for NetApp advanced memory solutions, including the MAX Data* memory tiering solution. MAX Data enables a plug-and-play approach to using Intel Optane DC persistent memory with a number of applications, providing access to persistent memory without changes to the application itself. In this interview, Ruiz speaks to the effects of today's data explosion and how NetApp is helping to address storage and data challenges for customers in an array of verticals including financial services, government, retail, and healthcare. Ruiz notes that simply having data is no longer enough -- what counts is the ability to analyze and quickly act on data. Ruiz additionally forecasts how advancements like persistent memory will influence storage architectures in the future, including making large-scale data analysis less expensive and more available to more organizations. By spanning across multiple servers, MAX Data enables persistent memory to be viewed as one continuous pool, multiplying by a factor of 25 the amount of persistent memory sitting on your servers[1]. NetApp testing has indicated that by reducing CPU wait time via efficient tiering, MAX Data can accelerate the performance of massively scalable database applications by up to 5x while significantly reducing infrastructure cost[2]. For more information on NetApp, please visit https://netapp.com. Software and workloads used in performance tests may have been optimized for performance only on Intel microprocessors. Performance tests, such as SYSmark and MobileMark, are measured using specific computer systems, components, software, operations and functions. Any change to any of those factors may cause the results to vary. You should consult other information and performance tests to assist you in fully evaluating your contemplated purchases, including the performance of that product when combined with other products. For more information go to www.intel.com/benchmarks. [1] For every 1TB of Intel Optane DC persistent memory, NetApp MAX Data v1.3 is designed to support 25TB of flash as a second tier. Please visit https://www.netapp.com/us/products/data-management-software/max-data.aspx for details. [2] 5x massively scalable database application acceleration with reduced infrastructure cost based on NetApp testing. Please visit https://www.netapp.com/us/products/data-management-software/max-data.aspx for details. Intel technologies' features and benefits depend on system configuration and may require enabled hardware, software or service activation. Performance varies depending on system configuration. No product or component can be absolutely secure. Check with your system manufacturer or retailer or learn more at intel.com. Intel, the Intel logo, and Optane are trademarks of Intel Corporation or its subsidiaries in the U.S. and/or other countries. *Other names and brands may be claimed as the property of others. © Intel Corporation

Brian Bulkowski, founder of Aerospike, joins Chip Chat to talk about how Aerospike is facilitating a new class of databases for Internet-scale customers. Aerospike is a database company that created a ground-up platform to support the larger datasets and operational databases driven by use cases like retail catalogs, fraud detection, and telecommunications. In this interview, Bulkowski discusses how Aerospike is working to support customers generating terabytes of data from billions of transactions every day and shares his thoughts on Intel® Optane™ DC persistent memory, which Aerospike has found to reduce the restart time for an 8.7 TB database by up to 135x[1]. For more information on Aerospike, please visit aerospike.com. [1] Tests performed by Intel and Aerospike as of 27 February 2019 demonstrated that an 8.7 TB database could be restarted in as little as 35 seconds on a server configured with DRAM + Intel® Optane™ DC persistent memory versus up to 4,745 seconds (1 hr 19 m 5 s) on a server configured with an equivalent amount of DRAM-only memory, for details see https://intel.ly/2vFT5m5. All information provided here is subject to change without notice. Contact your Intel representative to obtain the latest Intel product specifications and roadmaps. Intel processors of the same SKU may vary in frequency or power as a result of natural variability in the production process. For more information about performance and benchmark data, visit www.intel.com/benchmarks. Intel does not control or audit third-party benchmark data or the web sites referenced in this document. You should visit the referenced web site and confirm whether referenced data are accurate. Performance results are based on testing and may not reflect all publicly available security updates. See configuration disclosure for details. No product can be absolutely secure. Software and workloads used in performance tests may have been optimized for performance only on Intel microprocessors. Performance tests, such as SYSmark and MobileMark, are measured using specific computer systems, components, software, operations and functions. Any change to any of those factors may cause the results to vary. You should consult other information and performance tests to assist you in fully evaluating your contemplated purchases, including the performance of that product when combined with other products. Optimization Notice: Optimization Notice: Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice. Notice Revision #20110804 Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade. This interview contains information on products, services, and or processes in development. All information provided here is subject to change without notice. Contact your Intel representative to obtain the latest forecast, schedule, specifications, and roadmaps. The products and services described may contain defects or errors known as errata which may cause deviations from published specifications. Current characterized errata are available on request.

As the amount of data grows exponentially businesses are looking to leverage artificial intelligence (AI) to make real-time decisions with it. Yoav Einav, Vice President of Product at GigaSpaces, joins Intel on AI to discuss how the GigaSpaces InsightEdge platform is enabling enterprises to truly take advantage of their data utilizing in-memory computing for fast […]

In this episode of Chip Chat, Paul Nash, Product Manager Compute Engine on Google Cloud Platform at Google, discusses the industry trends impacting IaaS and how Google Cloud Platform together with Intel are driving innovation in the cloud. Together Google and Intel are optimizing hardware to support enterprise workloads including developing solutions for SAP HANA. Google Cloud Platform is also announcing a new family of instances that leverage Intel Optane DC Persistent Memory. Learn more about the benefits this new memory tier offers Google's customers along with more information on all the new instances being announced at Google Next 2019. For more information visit google.cloud.com. Intel technologies' features and benefits depend on system configuration and may require enabled hardware, software or service activation. Performance varies depending on system configuration. No product or component can be absolutely secure. Check with your system manufacturer or retailer or learn more at intel.com. Intel, Optane, and the Intel logo are trademarks of Intel Corporation or its subsidiaries in the U.S. and/or other countries. *Other names and brands may be claimed as the property of others. © Intel Corporation

Mike’s away so Chris joins Wes to discuss running your workstation from RAM, the disappointing realities of self driving cars, and handling the ups and downs of critical feedback.

SAP HANA User mit SUSE Linux Enterprise Server for SAP Applications erhalten Zugriff auf die neue Intel Optane DC Persistant Memory Technologie; Daten näher an den Prozessor bringen und Latenzen reduzieren...

Sponsored By:  NetApp In this episode we talk new persistent memory IO technology  with Andy Grimes, Principal Technologist, NetApp. Andy presented at the NetApp Insight 2018 TechFieldDay Extra (TFDx) event (video available here). If you get a chance we encourage you to watch the videos as Andy, did a great job describing their new MAX … Continue reading "75: GreyBeards talk persistent memory IO with Andy Grimes, Principal Technologist, NetApp"

Mitigating Spectre/Meltdown on HP Proliant servers, omniOS installation setup, debugging a memory corruption issue on OpenBSD, CfT for OpenZFS native encryption, Asigra TrueNAS backup appliance shown at VMworld, NetBSD 6 EoL, and more. ##Headlines How to mitigate Spectre and Meltdown on an HP Proliant server with FreeBSD As recently announced in a previous article I wanted to write a couple of guides on how to mitigate Spectre and Meltdown vulnerabilities in GNU/Linux and UNIX environments. It is always a good and I hope a standard practice to have your systems patched and if they aren’t for whatever the reason (that legacy thing you’re carrying on for ages) you may take the necessary extra steps to protect your environment. I never planned to do any article on patching anything. Nowadays it’s a no brainer and operating systems have provided the necessary tools for this to be easy and as smooth as possible. So why this article? Spectre and Meltdown are both hardware vulnerabilities. Major ones. They are meaningful for several reasons among them the world wide impact since they affect Intel and AMD systems which are ubiquitous. And second because patching hardware is not as easy, for the manufacturer and for the users or administrators in charge of the systems. There is still no known exploit around left out in the open hitting servers or desktops anywhere. The question is not if it will ever happen. The question is when will it happen. And it may be sooner than later. This is why big companies, governments and people in charge of big deployments are patching or have already patched their systems. But have you done it to your system? I know you have a firewall. Have you thought about CVE-2018-3639? This particular one could make your browser being a vector to get into your system. So, no, there is no reason to skip this. Patching these set of vulnerabilities implies some more steps and concerns than updating the operating system. If you are a regular Windows user I find rare you to be here and many of the things you will read may be foreign to you. I am not planning to do a guide on Windows systems since I believe someone else has or will do it and will do it better than me since I am not a pro Windows user. However there is one basic and common thing for all OS’s when dealing with Spectre and Meltdown and that is a microcode update is necessary for the OS patches to effectively work. What is microcode? You can read the Wikipedia article but in short it is basically a layer of code that allows chip manufacturers to deal with modifications on the hardware they’ve produced and the operating systems that will manage that hardware. Since there’s been some issues (namely Spectre and Meltdown) Intel and AMD respectively have released a series of microcode updates to address those problems. First series did come with serious problems and some regressions, to the point GNU/Linux producers stopped releasing the microcode updates through their release channels for updates and placed the ball on Intel’s roof. Patching fast does always include risks, specially when dealing with hardware. OS vendors have resumed their microcode update releases so all seems to be fine now. In order to update the microcode we’re faced with two options. Download the most recent BIOS release from our vendor, provided it patches the Spectre and Meltdown vulnerabilities, or patch it from the OS. If your hardware vendor has decided not to provide support on your hardware you are forced to use the latter solution. Yes, you can still keep your hardware. They usually come accompanied with a “release notes” file where there are some explanatory notes on what is fixed, what is new, etc. To make the search easy for you a news site collected the vendors list and linked the right support pages for anyone to look. In some scenarios it would be desirable not to replace the whole BIOS but just update the microcode from the OS side. In my case I should update an HP Proliant ML110 G7 box and the download link for that would be this. Instead of using the full blown BIOS update path we’ll use the inner utilities to patch Spectre and Meltdown on FreeBSD. So let’s put our hands on it See the article for the technical breakdown ###A look beyond the BSD teacup: OmniOS installation Five years ago I wrote a post about taking a look beyond the Linux teacup. I was an Arch Linux user back then and since there were projects like ArchBSD (called PacBSD today) and Arch Hurd, I decided to take a look at and write about them. Things have changed. Today I’m a happy FreeBSD user, but it’s time again to take a look beyond the teacup of operating systems that I’m familiar with. Why Illumos / OmniOS? There are a couple of reasons. The Solaris derivatives are the other big community in the *nix family besides Linux and the BSDs and we hadn’t met so far. Working with ZFS on FreeBSD, I now and then I read messages that contain a reference to Illumos which certainly helps to keep up the awareness. Of course there has also been a bit of curiosity – what might the OS be like that grew ZFS? Also the Ravenports project that I participate in planned to support Solaris/Illumos right from the beginning. I wanted to at least be somewhat “prepared” when support for that platform would finally land. So I did a little research on the various derivatives available and settled on the one that I had heard a talk about at last year’s conference of the German Unix Users Group: “OmniOS – Solaris for the Rest of Us”. I would have chosen SmartOS as I admire what Bryan Cantrill does but for getting to know Illumos I prefer a traditional installation over a run-from-RAM system. Of course FreeBSD is not run by corporations, especially when compared to the state of Linux. And when it comes to sponsoring, OpenBSD also takes the money… When it comes to FreeBSD developers, there’s probably some truth to the claim that some of them are using macOS as their desktop systems while OpenBSD devs are more likely to develop on their OS of choice. But then there’s the statement that “every innovation in the past decade comes from Solaris”. Bhyve alone proves this wrong. But let’s be honest: Two of the major technologies that make FreeBSD a great platform today – ZFS and DTrace – actually do come from Solaris. PAM originates there and a more modern way of managing services as well. Also you hear good things about their zones and a lot of small utilities in general. In the end it was a lack of time that made me cheat and go down the easiest road: Create a Vagrantfile and just pull a VM image of the net that someone else had prepared… This worked to just make sure that the Raven packages work on OmniOS. I was determined to return, though – someday. You know how things go: “someday” is a pretty common alias for “probably never, actually.” But then I heard about a forum post on the BSDNow! podcast. The title “Initial OmniOS impressions by a BSD user” caught my attention. I read that it was written by somebody who had used FreeBSD for years but loathed the new Code of Conduct enough to leave. I also oppose the Conduct and have made that pretty clear in my February post [ ! -z ${COC} ] && exit 1. As stated there, I have stayed with my favorite OS and continue to advocate it. I decided to stop reading the post and try things out on my own instead. Now I’ve finally found the time to do so. What’s next? That’s it for part one. In part two I’ll try to make the system useful. So far I have run into a problem that I haven’t been able to solve. But I have some time now to figure things out for the next post. Let’s see if I manage to get it working or if I have to report failure! ###What are all these types of memory in top(1)? Earlier this week I convinced Mark Johnston, one of the FreeBSD VM experts to update a page on the FreeBSD wiki that I saw was being referenced on stackoverflow and similar sites Mark updated the explanations to be more correct, and to include more technical detail for inquiring minds He also added the new type that appeared in FreeBSD somewhat recently Active - Contains memory “actively” (recently) being used by applications Inactive - Contains memory that has not been touched recently, or was released from the Buffer Cache Laundry - Contains memory that Inactive but still potentially contains useful data that needs to be stored before this memory can be used again Wired - Memory that cannot be swapped out, including the kernel, network stack, and the ZFS ARC Buf - Buffer Cache, used my UFS and most filesystems except ZFS (which uses the ARC) Free - Memory that is immediately available for use by the rest of the system ##News Roundup OpenBSD saves me again! — Debug a memory corruption issue Yesterday, I came across a third-part library issue, which crashes at allocating memory: Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f594a5a9b6b in _int_malloc () from /usr/lib/libc.so.6 (gdb) bt #0 0x00007f594a5a9b6b in _int_malloc () from /usr/lib/libc.so.6 #1 0x00007f594a5ab503 in malloc () from /usr/lib/libc.so.6 #2 0x00007f594b13f159 in operator new (sz=5767168) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/new_op.cc:50 It is obvious that the memory tags are corrupted, but who is the murder? Since the library involves a lot of maths computation, it is not an easy task to grasp the code quickly. So I need to find another way: (1) Open all warnings during compilation: -Wall. Nothing found. (2) Use valgrind, but unfortunately, valgrind crashes itself: valgrind: the 'impossible' happened: Killed by fatal signal host stacktrace: ==43326== at 0x58053139: get_bszB_as_is (m_mallocfree.c:303) ==43326== by 0x58053139: get_bszB (m_mallocfree.c:315) ==43326== by 0x58053139: vgPlain_arena_malloc (m_mallocfree.c:1799) ==43326== by 0x5800BA84: vgMemCheck_new_block (mc_malloc_wrappers.c:372) ==43326== by 0x5800BD39: vgMemCheck___builtin_vec_new (mc_malloc_wrappers.c:427) ==43326== by 0x5809F785: do_client_request (scheduler.c:1866) ==43326== by 0x5809F785: vgPlain_scheduler (scheduler.c:1433) ==43326== by 0x580AED50: thread_wrapper (syswrap-linux.c:103) ==43326== by 0x580AED50: run_a_thread_NORETURN (syswrap-linux.c:156) sched status: running_tid=1 (3) Change compiler, use clang instead of gcc, and hope it can give me some clues. Still no effect. (4) Switch Operating System from Linux to OpenBSD, the program crashes again. But this time, it tells me where the memory corruption occurs: Program terminated with signal SIGSEGV, Segmentation fault. #0 0x000014b07f01e52d in addMod (r=, a=4693443247995522, b=28622907746665631, I figure out the issue quickly, and not bother to understand the whole code. OpenBSD saves me again, thanks! ###Native Encryption for ZFS on FreeBSD (Call for Testing) To anyone with an interest in native encryption in ZFS please test the projects/zfs-crypto-merge-0820 branch in my freebsd repo: https://github.com/mattmacy/networking.git git clone https://github.com/mattmacy/networking.git -b projects/zfs-crypto-merge-0820 The UI is quite close to the Oracle Solaris ZFS crypto with minor differences for specifying key location. Please note that once a feature is enabled on a pool it can’t be disabled. This means that if you enable encryption support on a pool you will never be able to import it in to a ZFS without encryption support. For this reason I would strongly advise against using this on any pool that can’t be easily replaced until this change has made its way in to HEAD after the freeze has been lifted. By way of background the original ZoL commit can be found at: https://github.com/zfsonlinux/zfs/pull/5769/commits/5aef9bedc801830264428c64cd2242d1b786fd49 ###VMworld 2018: Showcasing Hybrid Cloud, Persistent Memory and the Asigra TrueNAS Backup Appliance During its last year in Las Vegas before moving back to San Francisco, VMworld was abuzz with all the popular buzzwords, but the key focus was on supporting a more agile approach to hybrid cloud. Surveys of IT stakeholders and analysts agree that most businesses have multiple clouds spanning both public cloud providers and private data centers. While the exact numbers vary, well over half of businesses have a hybrid cloud strategy consisting of at least three different clouds. This focus on hybrid cloud provided the perfect timing for our announcement that iXsystems and Asigra are partnering to deliver the Asigra TrueNAS Backup Appliance, which combines Asigra Cloud Backup software backed by TrueNAS storage. Asigra TrueNAS Backup Appliances provide a self-healing and ransomware-resistent OpenZFS backup repository in your private cloud. The appliance can simultaneously be used as general-purpose file, block, and object storage. How does this tie in with the hybrid cloud? The Asigra Cloud Backup software can backup data from public cloud repositories – G Suite, Office 365, Salesforce, etc. – as well as intelligently move backed-up data to the public cloud for long-term retention. Another major theme at the technical sessions was persistent memory, as vSphere 6.7 added support for persistent memory – either as a storage tier or virtualized and presented to a guest OS. As detailed in our blog post from SNIA’s Persistent Memory Summit 2018, persistent memory is rapidly becoming mainstream. Persistent memory bridges the gap between memory and flash storage – providing near-memory latency storage that persists across reboots or power loss. vSphere allows both legacy and persistent memory-aware applications to leverage this ultra-fast storage tier. We were excited to show off our newly-introduced TrueNAS M-Series at VMworld, as all TrueNAS M40 and M50 models leverage NVDIMM persistent memory technology to provide a super-fast write cache, or SLOG, without any of the limitations of Flash technology. The iXsystems booth’s theme was “Enterprise Storage, Open Source Economics”. iXsystems leverages the power of Open Source software, combined with our enterprise-class hardware and support, to provide incredibly low TCO storage for virtualization environments. Our TrueNAS unified storage and server offerings are an ideal solution for your organization’s private cloud infrastructure. Combined with VMware NSX Hybrid Connect – formerly known as VMware Hybrid Cloud Extension – you can seamlessly shift running systems into a public cloud environment for a true hybrid cloud solution. Another special treat at this year’s booth was iXsystems Vice President of Engineering Kris Moore giving demos of an early version of “Project TrueView”, a single-pane of glass management solution for administration of multiple FreeNAS and TrueNAS systems. In addition to simplified administration and enhanced monitoring, Project TrueView will also provide Role-Based Access Control for finer-grained permissions management. A beta version of Project TrueView is expected to be available at the end of this year. Overall, we had a great week at VMworld 2018 with lots of good conversations with customers, press, analysts, and future customers about TrueNAS, the Asigra TrueNAS Backup Appliance, iXsystems servers, Project TrueView, and more – our booth was more popular than ever! ###End of life for NetBSD 6.x In keeping with NetBSD’s policy of supporting only the latest (8.x) and next most recent (7.x) major branches, the recent release of NetBSD 8.0 marks the end of life for NetBSD 6.x. As in the past, a month of overlapping support has been provided in order to ease the migration to newer releases. As of now, the following branches are no longer maintained: netbsd-6-1 netbsd-6-0 netbsd-6 This means: There will be no more pullups to those branches (even for security issues) There will be no security advisories made for any those branches The existing 6.x releases on ftp.NetBSD.org will be moved into /pub/NetBSD-archive/ May NetBSD 8.0 serve you well! (And if it doesn’t, please submit a PR!) ##Beastie Bits Blast from the past: OpenBSD 3.7 CD artwork People are asking about scale of BSD projects. Let’s figure it out… Tuesday, 21 August 18: me, on ed(1), at SemiBUG arm64 gains RETGUARD Call for participation FreeBSD-UPB/bhyvearm64-utils ##Feedback/Questions Eric - FreeNAS for Vacation Patrick - Long Live Unix Jason - Jason - Full MP3 Recordings Bostjan - Question about jails and kernel Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv

The Q2 earnings announcement from “camera company” Snap was good from a revenue and earnings perspective but sour from a user growth perspective – it lost 3m users! Is this part of a larger shift that we've seen with Facebook and Twitter? Should we be evaluating social media (and camera) companies differently? Plus our Fast Five: Intel's Persistent Memory, Qualcomm's 5G Antennas and its litigation win, the "new" Salesforce CEO, and Apple's Tesla grab. Plus a Chip Company that WannaCry and the sticky issue of Twitter, Jack Dorsey, and a fringe conspiracy theorist by the name of Alex Jones. This episode features: Daniel Newman (@danielnewmanuv), Olivier Blanchard (@oablanchard), Fred McClimans (@fredmcclimans). If you haven't already, please subscribe to our show on iTunes or SoundCloud. For inquiries or more information on the show you may email the team at info@futurumresearch.com or follow @FuturumXYZ on Twitter and feel free to direct inquires through that channel as well. To learn more about Future research please visit www.futurumresearch.com As a reminder, the Futurum Tech Podcast is intended as an informational newsletter only. No investment advice is offered. While equities are frequently discussed, no investment advice is offered or implied.

Jennifer Huffstetler, Vice President and General Manager for Data Center Product Marketing, Product Management, and Storage at Intel Corporation, joins Chip Chat to discuss developer and industry excitement for Intel® Optane™ DC Persistent Memory. Intel Optane DC Persistent Memory represents a rare opportunity to re-architect the storage hierarchy by bringing affordable, high-capacity memory closer to the CPU, accelerating workloads and speeding the delivery of applications. In this interview, Huffstetler speaks to the key benefits that Intel Optane DC Persistent Memory will deliver to end users and how Intel is working to support the development community to enable best use of this groundbreaking technology. Resources for Intel Optane DC Persistent Memory now have reached more than 100,000 developers and see more than 10,000 developer users each month. Intel Optane DC Persistent Memory will be available for first access by the end of 2018. For more information on Intel Optane DC Persistent Memory, please visit pmem.io. 9x more read transactions (ops/sec) and 11x more users per system vs. comparable server system with DRAM and NAND NVMe drives when using Apache* Cassandra-4.0 results have been estimated based on tests conducted on pre-production systems, and provided to you for informational purposes. Software and workloads used in performance tests may have been optimized for performance only on Intel microprocessors. Performance tests, such as SYSmark and MobileMark, are measured using specific computer systems, components, software, operations and functions. Any change to any of those factors may cause the results to vary. You should consult other information and performance tests to assist you in fully evaluating your contemplated purchases, including the performance of that product when combined with other products. For more information go to www.intel.com/benchmarks. The benchmark results may need to be revised as additional testing is conducted. The results depend on the specific platform configurations and workloads utilized in the testing, and may not be applicable to any particular user's components, computer system or workloads. The results are not necessarily representative of other benchmarks and other benchmark results may show greater or lesser impact from mitigations. Intel technologies’ features and benefits depend on system configuration and may require enabled hardware, software or service activation. Performance varies depending on system configuration. No computer system can be absolutely secure. Check with your system manufacturer or retailer or learn more at intel.com. Intel, the Intel logo, and Optane are trademarks of Intel Corporation or its subsidiaries in the U.S. and/or other countries. *Other names and brands may be claimed as the property of others. © Intel Corporation.

Soroush interviews Chris about his experience at this year’s Strange Loop conference.Strange LoopStrange Loop Schedule (currently showing the 2017 schedule)Alex Miller"Just-So Stories For AI: Explaining Black-Box Predictions" By Sam RitchieDecision Tree LearningRandom Forest""It Me": Under The Hood Of Web Authentication" By Yan Zhu, Garrett RobinsonLito Nikolai"Level Up Your Concurrency Skills With Rust" By David SullinsSwift Ownership ManifestoCity Museum"To Serve The People: Public Interest Technologists" By Matt Mitchell"Redux: Architecting And Scaling A New Web App At The Ny Times" By Juan Carlos Montemayor Elosua"The Holy Grail Of Systems Analysis: From What To Where To Why" By Daniel Spoonhower"Biomaterials As Ui" By Ruthie NachmanyTalks Chris hasn’t watched yet, but wants to"Keeping Time In Real Systems" By Kavya Joshi"Stop Rate Limiting! Capacity Management Done Right" By Jon Moore"Dependent Types In Haskell" By Stephanie Weirich"Observability For Emerging Infra: What Got You Here Won't Get You There" By Charity Majors"The Security of Classic Game Consoles" by Kevin Shekleton"Key to the City: Writing Code to Induce Social Change" by Jurnell Cockhren"The Future is Now" by Rachel White"Experimental Creative Writing with the Vectorized Word" by Allison Parrish"Antics, drift, and chaos" by Lorin Hochstein"Lazy Defenses: Using Scaled TTLs to Keep Your Cache Correct" by Bonnie Eisenman"Promise and Pitfalls of Persistent Memory" by Rob DickinsonPre-ShowChris’s Aircraft Radar Alexa skillSelfridge Air National Guard BaseYankee Air Museum (Ypsilanti, MI)Get a new Fatal Error episode every week by becoming a supporter at patreon.com/fatalerror.

Prof. Dr. Alexander Zeier, Global Managing Director for In-Memory Solutions (incl. HANA/S4HANA) at Accenture, and Mike Ferron-Jones, Product Line Manager for Intel Persistent Memory Solutions, join us to discuss the incredible potential of Intel persistent memory. At SAP SAPPHIRE NOW 2017, Intel demonstrated an SAP HANA instance running on a platform utilizing both DRAM and Intel persistent memory. In this discussion, Ferron-Jones talks about Intel persistent memory's most-exciting features, and how large, affordable, non-volatile memory will drive a revolution in application development and service delivery. Then, Dr. Zeier speaks to Intel persistent memory's ability to eliminate memory size bottlenecks and accelerate workloads like machine learning, deep learning, and advanced analytics. Finally, the two discuss Intel's collaboration with Accenture and SAP to ensure that SAP HANA will take full advantage when Intel persistent memory is made available to end customers in 2018. For more information on Intel persistent memory, please read Ferron-Jones' recent post on the IT Peer Network (http://intel.ly/2rnH2X5) and check out the software-development resources at http://pmem.io/.

Storage is getting incredibly hot again with the parallel developments of NVMe, persistent memory technology, Swordfish management and active archiving. Host Marc Farley (@GoFarley) is joined by Mark Carlson (@macsun), Richelle Ahlvers (@rahlvers), Shaun Walsh (@cingulus), Mark Pastor (@markpastor), Stephen Bates (@stepbates), Tom Coughlin (@thomasacoughlin) and Jim Handy (objective-analysis.com/) .

The Flash Memory Summit is an annual gathering of “People Making Flash Products Happen”.   The conference was held in Santa Clara August 9-11, 2016.  EMC was a premium sponsor of the event, showcasing the latest in AL-FLASH product design and direction.   In addition, EMC was invited to participate in the General Keynote Sessions.  EMC Fellow, Vice President of Emerging Media and friend of EMC The Source Podcast, Dan Cobb (@dcobbweb), hosted the Keynote – “Flash Storage Meets Persistent Memory – The Modern Data Center Changes Forever!”  I was able to catch up with Dan as he headed into his keynote address.  That interview and the full content of the Keynote Session are this week’s EMC The Source Podcast. Don’t miss “EMC The Source” app in the App Store.  Be sure to subscribe to The Source Podcast on iTunes, Stitcher Radio or Google Play and visit the official blog at thesourceblog.emc.com EMC: The Source Podcast is hosted by Sam Marraccini (@SamMarraccini)

In this podcast, Ryan Baxter from Micron describes the company’s new NVDIMM persistent memory products. Today Micron announced the production of 8GB DDR4 NVDIMM, the company’s first commercially available solution in the persistent memory category. Persistent memory delivers a unique balance of latency, bandwidth, capacity and cost, delivering ultra-fast DRAM-like access to critical data and allowing system designers to better manage overall costs. With persistent memory, system architects are no longer forced to sacrifice latency and bandwidth when accessing critical data that must be preserved. Watch the video presentation.

We show that for particles performing Brownian motion in a frozen array of scatterers long-time correlations emerge in the mean-square displacement. Defining the velocity autocorrelation function (VACF) via the second time-derivative of the mean-square displacement, power-law tails govern the long-time dynamics similar to the case of ballistic motion. The physical origin of the persistent memory is due to repeated encounters with the same obstacle which occurs naturally in Brownian dynamics without involving other scattering centers. This observation suggests that in this case the VACF exhibits these anomalies already at first order in the scattering density. Here we provide an analytic solution for the dynamics of a tracer for a dilute planar Lorentz gas and compare our results to computer simulations. Our result support the idea that quenched disorder provides a generic mechanism for persistent correlations irrespective of the microdynamics of the tracer particle