Meego aptcms2010

Linaro has multiple labs and board farms with varying purposes. This session will start with an overview of each of these, their locations, their focus, etc. It will then provide examples and direction on how a Member can add their hardware to a board farm. It will also provide an overview of how a Member or employee can navigate/leverage/check out a board for experimentation and usage (this varies based upon which lab/board farm is being considered, so all will be reviewed) in each of the farm locations. Finally, the session will provide pointers to any respective documentation, user guides, etc. for each of the locations.

BKK16-213 Where's the Hardware?

Data centre networking at London School of Economics and Political Science - ...

Jisc

GTPing, How To

Kentaro Ebisawa

Nb iot-nfapi-implementation-1

Yafie Abdillah

BKK16-505 Kernel and Bootloader Consolidation and Upstreaming

The linux kernel has two distinct ways of managing idle. The CPUidle framework for CPUs and for all other devices: runtime PM combined with generic power domains (genpd). In addition, CPUidle is not scaling well for multi-cluster SMP systems and heterogeneous systems like big.LITTLE. To better manage idle for modern SoCs with a hierarchical structure, we are exploring extending runtime PM and genpd to CPUs so there is a unified framework for managing idle across all devices.

BKK16-410 SoC Idling & CPU Cluster PM

At Qt Day 2019 in Florence, Italy, I gave a presentation about "Using Qt under LGPLv3". In the first part, I go through Section "4. Combined Works" and explain the obligations of LGPLv3 in detail. When you combine your application with the Qt libraries, you can keep closed the source code of the application and publish the application and the Qt libraries under your license terms. You must satisfy the following conditions. On a physical medium like a USB drive or DVD, you must provide the source code of the Qt libraries, the text of the LGPLv3 and GPLv3, the Copyright notices of the Qt libraries, a description of your modification of the Qt libraries and the installation information. If your application has a user interface, you must display the license texts of the LGPLv3 and GPLv3 and the Copyright notices in this user interface. The installation information - a.k.a. the anti-tivoisation clause - describes how the user can build a modified version of Qt, how to install this version on the device, and how to run the application with the modified Qt version on the device. If you build a B2B product, you need not provide the installation information. In the second part, I compare the costs of Qt Commercial and Qt LGPLv3. You must check the licenses for all packages of the (embedded) Linux system, no matter whether you use Qt Commercial or Qt LGPLv3. Qt commercial adds per-developer fees and per-unit fees (royalties). If you use Boot2Qt, Qt for Automation, Qt Safe Renderer or other commercial add-ons, Qt Commercial may well be worth the additional costs. In the third part, I show how Yocto (bitbake) and Fossology help with the compliance checks. Fossology is a license and copyright scanner.

2015.7.17 JANOG36 BGP Flowspec Interoperability Test @ Interop Tokyo 2015 Sho...

Shuichi Ohkubo

LF_DPDK17_Accelerating P4-based Dataplane with DPDK

LF_DPDK

Using Qt under LGPLv3

Burkhard Stubert

LAS16-500: The Rise and Fall of Assembler and the VGIC from Hell Speakers: Marc Zyngier, Christoffer Dall Date: September 30, 2016 ★ Session Description ★ KVM/ARM has grown up. While the initial implementation of virtualization support for ARM processors in Linux was a quality upstream software project, there were initial design decisions simply not suitable for a long-term maintained hypervisor code base. For example, the way KVM/ARM utilized the hardware support for virtualization, was by running a ‘switching’ layer of code in EL2, purely written in assembly. This was a reasonable design decision in the initial implementation, as the switching layer only had to do one thing: Switch between a VM and the host. But as we began to optimize the implementation, add support for ARMv8.1 and VHE, and added features such as debugging support, we had to move to a more integrated approach, writing the switching logic in C code as well. As another example, the support for virtual interrupts, famously known as the VGIC, was designed with a focus on optimizing MMIO operations. As it turns out, MMIO operations is a less important and infrequent operation on the GIC, and the design had some serious negative consequences for supporting other state transitions for virtual interrupts and had negative performance implications. Therefore, we completely redesigned the VGIC support, and implemented the whole thing from scratch as a team effort, with a very promising result, upstream since Linux v4.7. In this talk we will cover the evolution of this software project and give an overview of the state of the project as it is today. ★ Resources ★ Etherpad: pad.linaro.org/p/las16-500 Presentations & Videos: http://connect.linaro.org/resource/las16/las16-500/ ★ Event Details ★ Linaro Connect Las Vegas 2016 – #LAS16 September 26-30, 2016 http://www.linaro.org http://connect.linaro.org

LAS16-500: The Rise and Fall of Assembler and the VGIC from Hell

BKK16-403 Android HAL Consolidation Status

The recent surge of network I/O performance has put enormous pressure on memory and software I/O processing subsystems for many cloud and data center applications, such as key-value stores and real-time analytics frameworks. A major reason for the high memory and processing overheads is the inefficient use of these resources by network interface cards. Offloading functionality to a programmable NIC can help, but what to offload needs to be carefully chosen. This presentation will cover a number of reusable offloading mechanisms that can help data center software processing efficiency. It will show how to implement these mechanisms in the P4 programming language and discuss their efficiency using experiments run on the Netronome Agilio-CX NIC.

Accelerating Networked Applications with Flexible Packet Processing

ARM server hardware will be shipping in 2016. An incredible amount of work has been done to get this far -- defining and implementing industry standards used by servers, development and testing of SoCs, and all sorts of Linux kernel work. So, how do we make sure we meet all these industry standards? To a great extent, we've relied on magical thinking so far. That works, but only for so long. LuvOS and FWTS were created in order to catch many of the problems users have found; in this presentation, we describe how we have started extending FWTS to check for standards compliance, specifically ACPI and the SBBR, and how we can use LuvOS to run FWTS and other test suites so that we can rely on hard data, and not just wishful thinking.

BKK16-400A LuvOS and ACPI Compliance Testing

AS201701 - Building an Internet backbone with pure 1he servers and Linux

Maximilan Wilhelm

BKK16-506 PMWG Farm

Developing SDN apps in Ryu

Che Wei Lin

Transparent eBPF Offload: Playing Nice with the Linux Kernel

Network measurement has been playing a crucial role in network operations since it cannot only detect the anomalies, but also facilitate traffic engineering. With the recent development of P4 language, network measurement is one of the data plane applications that can benefit from the programmability enabled by P4. However, P4 does not support general purpose language structures such as for-loop, and the if-statement can only be used in its control block, and it has only a limited set of primitive actions. Hence, the current P4 has its limitations to support complicated measurement functions. In this webinar, we implement and evaluate the Count-Min sketch (used for heavy hitter detection) using the combination of P4 and C on a Netronome NFP NIC. We plan to demonstrate the flexibility and performance of the design and the C plug-in feature of Netronome NFP.

Whitebox Switches Deployment Experience

APNIC

Network Measurement with P4 and C on Netronome Agilio

FLAR - Fondo Latinoamericano para Arroz de Riego

What's hot (20)

Measuring a 25 and 40Gb/s Data Plane

BKK16-213 Where's the Hardware?

Data centre networking at London School of Economics and Political Science - ...

GTPing, How To

Nb iot-nfapi-implementation-1

BKK16-505 Kernel and Bootloader Consolidation and Upstreaming

BKK16-410 SoC Idling & CPU Cluster PM

2015.7.17 JANOG36 BGP Flowspec Interoperability Test @ Interop Tokyo 2015 Sho...

LF_DPDK17_Accelerating P4-based Dataplane with DPDK

Using Qt under LGPLv3

LAS16-500: The Rise and Fall of Assembler and the VGIC from Hell

BKK16-403 Android HAL Consolidation Status

Accelerating Networked Applications with Flexible Packet Processing

BKK16-400A LuvOS and ACPI Compliance Testing

AS201701 - Building an Internet backbone with pure 1he servers and Linux

BKK16-506 PMWG Farm

Developing SDN apps in Ryu

Transparent eBPF Offload: Playing Nice with the Linux Kernel

Whitebox Switches Deployment Experience

Network Measurement with P4 and C on Netronome Agilio

Viewers also liked

001 bacterial panicle blight, milton rush

Valentines dance 2013

Frances O'Neill

Web 2.0 as a tool for future teachers and students

Lis Faurholt

La Boite Chang3

agencelaboite

специальное предложение

Nati987

Social media effect on family

KayGruhlkey

Open Webforum: Twitterkanal von geo.admin.ch

Vom Informations- zum Interaktionsportal

Maria Gager

aeraproperty

Impulspräsentation zu ch.ch

Erwartungen an e-Gov

ch.ch 2020