HW API internal meeting 2/10/2001 Eric CANO, CERN/EP-CMD1 What’s proposed? l Integration with Christoph’s generic hardware access library for user-friendly.

Slides:

Advertisements

Similar presentations

System Area Network Abhiram Shandilya 12/06/01. Overview Introduction to System Area Networks SAN Design and Examples SAN Applications.

Advertisements

1/1/ / faculty of Electrical Engineering eindhoven university of technology Processor support devices Part 1:Interrupts and shared memory dr.ir. A.C. Verschueren.

Chapter 6 Security Kernels.

04/14/2008CSCI 315 Operating Systems Design1 I/O Systems Notice: The slides for this lecture have been largely based on those accompanying the textbook.

Silberschatz, Galvin and Gagne  Operating System Concepts Chapter 13: I/O Systems I/O Hardware Application I/O Interface Kernel I/O Subsystem.

Architectural Support for Operating Systems. Announcements Most office hours are finalized Assignments up every Wednesday, due next week CS 415 section.

I/O Hardware n Incredible variety of I/O devices n Common concepts: – Port – connection point to the computer – Bus (daisy chain or shared direct access)

Embedded Real-time Systems The Linux kernel. The Operating System Kernel Resident in memory, privileged mode System calls offer general purpose services.

Chapter 13: I/O Systems I/O Hardware Application I/O Interface

OPERATING SYSTEMS Introduction

Device Driver for Generic ASC Module - Project Presentation - By: Yigal Korman Erez Fuchs Instructor: Evgeny Fiksman Sponsored by: High Speed Digital Systems.

Process Concept An operating system executes a variety of programs

1 I/O Management in Representative Operating Systems.

Chapter 5 Input/Output I/O Hardware I/O Software Software Layers Tanenbaum, Modern Operating Systems 3 e, (c) 2008 Prentice-Hall, Inc. All rights.

UQC113S2 Interrupt driven IO. We have already seen the hardware support required to facilitate interrupts We will now look at the higher levels of software.

ThreadsThreads operating systems. ThreadsThreads A Thread, or thread of execution, is the sequence of instructions being executed. A process may have.

Operating Systems Concepts 1. A Computer Model An operating system has to deal with the fact that a computer is made up of a CPU, random access memory.

OSI and Architecture Independent Device Driver Jim Chen HYTEC ELECTRONICS LIMITED Spring 2013 – Diamond Light Source.

Chapter 13: I/O Systems I/O Hardware Application I/O Interface

I/O Tanenbaum, ch. 5 p. 329 – 427 Silberschatz, ch. 13 p

UNIX System Administration OS Kernal Copyright 2002, Dr. Ken Hoganson All rights reserved. OS Kernel Concept Kernel or MicroKernel Concept: An OS architecture-design.

SLAAC Hardware Status Brian Schott Provo, UT September 1999.

Cpr E 308 Input/Output Recall: OS must abstract out all the details of specific I/O devices Today –Block and Character Devices –Hardware Issues – Programmed.

1 Micro-kernel. 2 Key points Microkernel provides minimal abstractions –Address space, threads, IPC Abstractions –… are machine independent –But implementation.

I/O Systems I/O Hardware Application I/O Interface

How Hardware and Software Work Together

GBT Interface Card for a Linux Computer Carson Teale 1.

The Linux /proc Filesystem CSE8343 – Fall 2001 Group A1 – Alex MacFarlane, Garrick Williamson, Brad Crabtree.

LINUX System : Lecture 7 Bong-Soo Sohn Lecture notes acknowledgement : The design of UNIX Operating System.

CMS ECAL Week, July 20021Eric CANO, CERN/EP-CMD FEDkit FED Slink64 readout kit Dominique Gigi, Eric Cano (CERN EP/CMD)

Nevis FVTX Update Dave Winter FVTX Silicon Meeting 13 July 2006.

Update on ALICE software status and ideas Ervin Dénes Wigner Research Center Hungarian Academy of Sciences.

UNIX Unit 1- Architecture of Unix - By Pratima.

System Components ● There are three main protected modules of the System  The Hardware Abstraction Layer ● A virtual machine to configure all devices.

A. Frank - P. Weisberg Operating Systems Structure of Operating Systems.

Chapter 13 – I/O Systems (Pgs ). Devices  Two conflicting properties A. Growing uniformity in interfaces (both h/w and s/w): e.g., USB, TWAIN.

Operating-System Structures

Migration to PPC at JLab Richard Dickson. VME data interface differences: CPU VMEchip2 VME mvme177 System Local Bus PPC 750 CPU Raven VME mvme2700.

Input Output Techniques Programmed Interrupt driven Direct Memory Access (DMA)

Security Architecture and Design Chapter 4 Part 2 Pages 319 to 357.

Silberschatz, Galvin, and Gagne  Applied Operating System Concepts Module 12: I/O Systems I/O hardwared Application I/O Interface Kernel I/O.

System Programming Basics Cha#2 H.M.Bilal. Operating Systems An operating system is the software on a computer that manages the way different programs.

Major OS Components CS 416: Operating Systems Design, Spring 2001 Department of Computer Science Rutgers University

Part IVI/O Systems Chapter 13: I/O Systems. I/O Hardware a typical PCI bus structure 2.

1 Chapter 2: Operating-System Structures Services Interface provided to users & programmers –System calls (programmer access) –User level access to system.

Experimental Software Engineering Course for Training Practitioners in Embedded Real-Time Systems Real-Time Systems LAB, School of Electronic Engineering,

Introduction to Operating Systems Concepts

Computer System Structures

Input/Output (I/O) Important OS function – control I/O

Virtualization.

Hardware and OS Design and Layout.

Module 12: I/O Systems I/O hardware Application I/O Interface

Chapter 13: I/O Systems Modified by Dr. Neerja Mhaskar for CS 3SH3.

Interrupts and Interrupts Handling

Chapter 5: Threads Overview Multithreading Models Threading Issues

Chapter 5: Threads Overview Multithreading Models Threading Issues

Input/Output 1 1.

Linux device driver development

OS Virtualization.

I/O Systems I/O Hardware Application I/O Interface

Operating System Concepts

13: I/O Systems I/O hardwared Application I/O Interface

Integrating DPDK/SPDK with storage application

B.Ramamurthy Chapter 2 : Appendix

LINUX System : Lecture 7 Lecture notes acknowledgement : The design of UNIX Operating System.

Chapter 13: I/O Systems I/O Hardware Application I/O Interface

Computer System Structures

Operating Systems Structure

Module 12: I/O Systems I/O hardwared Application I/O Interface

Presentation transcript:

HW API internal meeting 2/10/2001 Eric CANO, CERN/EP-CMD1 What’s proposed? l Integration with Christoph’s generic hardware access library for user-friendly functions. l Addition on generic read-write functions (instead of only message passing in xdaq-shell) l Creation of a Generic access utility for i2ocore/xdaq- shell (could also serve as an example for i2ocore users) l Creation of PCI memory space mapping functionnality

HW API internal meeting 2/10/2001 Eric CANO, CERN/EP-CMD2 I 2 O core architecture (Linux) (updated) PCI bus Reserved memory for DMA (physmem) Kernel space Xdaq-shell messaging Interrupts Slave accesses PCI device DMA engine DMA Address translation Xdaq-shell Dbuffs Slave accesses Interrupts Mapping (no copy)Message passing (copies) Xdaq-shell messages Xdaq-shell Dbuffs User space (applications, paged memory) I 2 O core API New proposal In red & italic Xdaq-shell PCIMaps Mapping (no copy) Generic R/W module I 2 O core user’s module

HW API internal meeting 2/10/2001 Eric CANO, CERN/EP-CMD3 Proposal layout for the hardware integration and for VME l VME interfaces usually come with a driver, in user space already, let’s use it when it’s there. l The final user (system integrator) wants a nice interface to the hardware (possibly C++) l The C++ interface is application oriented and hides the hardware implementation as much as possible.

HW API internal meeting 2/10/2001 Eric CANO, CERN/EP-CMD4 Layout of hardware to C++, PCI and VME Final application OO library VboardOO library Pboard1OO library Pboard2 Real hardware Kernel space User space Xdaq-Shell Christoph’s interface VME interface Driver and API (e.g. NI-VISA) USER PROVIDED Unless Sergio decided Christoph’s interface I2o core for PCI User’s moduleGeneric module