Suresh’s bio: Dr. Suresh Gopalakrishnan is the corporate vice president and general manager of AMD’s server business. He is responsible for driving the end-to-end business execution of AMD server solutions worldwide. Under his leadership, AMD is pursuing a server strategy that leverages AMD’s broad IP portfolio to deliver disruptive products for the virtualized datacenter, software defined storage, high performance data analytics and IoT infrastructure. Prior to joining the company in June 2012, Dr. Gopalakrishnan served as vice president of engineering at Extreme Networks, a leader in high-performance Ethernet switching for cloud, data center, and mobile networks. During his tenure at Extreme Networks, Dr. Gopalakrishnan was also vice president of marketing and product management, as well as general manager of multiple business units. He has led large product teams that have defined and delivered Ethernet switching systems to enterprise, data center and carrier markets. He also has a strong semiconductor background in designing and leading teams that delivered CPUs, workstation chipsets, digital signal processors, and networking ASICs.
Prior to Extreme Networks, Dr. Gopalakrishnan held a variety of leadership positions at Riverstone Networks/Cabletron Systems, ZSP Corporation, Sun Microsystems and HP.
Dr. Gopalakrishnan holds a Ph.D. in Electrical Engineering from the University of Idaho and has completed the Advanced Executive Program at Northwestern University’s Kellogg School of Management. He is based in Sunnyvale, California.
One of the features introduced by the Android Runtime (ART) is an Ahead-Of-Time (AOT) compiler, named “Quick”, officially released with Android 5.0 Lollipop last year. The next release of the system due this year, Android M, features a new compiler, called “Optimizing”, fully developed in the Android Open Source Project (AOSP). Roland and Calin will present this new compiler, its design and implementation, the benefits brought by Optimizing, and some issues we faced during its development
This session is an advanced course on Linux kernel upstreaming fundamentals. The course covers how the arm-soc kernel tree is maintained and why that is important to ARM Linux kernel developers. The focus of the course is the explanation of the detailed mechanics of creating and posting patch series to upstream mailing lists for several common cases. Annotated session content is made up of previously upstreamed ARM support captured from emails to the kernel mailing lists. The target audience is both software engineers and engineering managers preparing to upstream software into the kernel. The topic requires a solid background in software configuration management terminology and the git SCM tool as well as a good technical understanding of the Linux kernel itself.
This presentation gives an overview of how various components of set-top software are integrated to provide a W3C EME solution employing a commercial DRM integrated with an open source TEE running on ARM TrustZone.
Thanks to an amazing community the Linux kernel is one of the most tested projects, or is it? Do systems like kernelci.org provide value? What is the current state of kernelci.org? Is there more we can do?
LEG has been optimizing Ceph, HDFS, Swift and kernel file system CRC algorithms, the session will describe the speed up and patch upstreaming and will then cover how to improve the collaboration and synergy with the Linaro Kernel working group.
Abstract: Experiences productizing the gateway (from hobby to product) and the challenges for IoT deployment scenarios: Home security, Home automation, Home healthcare, and Enterprise IoT (smart manufacturing).
In this session, Tim Bird will discuss the mainline status of several ARM SoCs used in mobile products. The average phone uses kernel software that is 3 years old, 20 versions behind mainline, and has 1 to 3 million lines of code out-of-tree. Tim will describe the “Device Mainlining” project of the Linux Foundation CE Workgroup, which seeks to address this problem. Some of the activities of this project are:
* publishing tools for mainline analysis
* finding big areas where multiple vendors have code out of tree
* identifying institutional barriers to corporate developer mainlining, and addressing them through education, training, and collaboration
* working with upstream to address deficient sub-systems or needed maintainer assistance
It is hoped that discussion will ensue about ways to continue enhancing this work, to get more SoC code mainlined.