DOCSLIB.ORG

Document Version Publisher Pdf

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Document Version Publisher Pdf Kent Academic Repository Full text document (pdf) Citation for published version Brown, Neil C.C. and Welch, Peter H. (2003) An Introduction to the Kent C++CSP Library. In: Communicating Process Architectures 2003, SEP 07-10, 2003, UNIV Twente, Enschde, Nederlands. DOI Link to record in KAR http://kar.kent.ac.uk/13921/ Document Version Publisher pdf Copyright & reuse Content in the Kent Academic Repository is made available for research purposes. Unless otherwise stated all content is protected by copyright and in the absence of an open licence (eg Creative Commons), permissions for further reuse of content should be sought from the publisher, author or other copyright holder. Versions of research The version in the Kent Academic Repository may differ from the final published version. Users are advised to check http://kar.kent.ac.uk for the status of the paper. Users should always cite the published version of record. Enquiries For any further enquiries regarding the licence status of this document, please contact: [email protected] If you believe this document infringes copyright then please contact the KAR admin team with the take-down information provided at http://kar.kent.ac.uk/contact.html Communicating Process Architectures – 2003 139 Jan F. Broenink and Gerald H. Hilderink (Eds.) IOS Press, 2003 An Introduction to the Kent C++CSP Library Neil BROWN and Peter WELCH Computing Laboratory, University of Kent, Canterbury, Kent, CT2 7NF, England. [email protected], [email protected] Abstract. This paper reports on a CSP library for C++, developed over the past year at the University of Kent. It is based on the OO-design and API of JCSP and the lightweight algorithms of KRoC occam, with extensions to exploit specific C++ ca- pabilities (such as templates). Both user-level and operating system threads are used to provide a range of implementation options and semantics (e.g. for managing block- ing system calls intelligently) that run efficiently under either Windows or Linux. The library is presented from the user’s point of view, mainly by way of a tutorial. Im- plementation details are also outlined and some benchmark results given. The per- formance of C++CSP is between that of KRoC occam and JCSP — fairly close to KRoC. 1 Background This year sees the 25th anniversary of C.A.R. Hoare’s paper describing Communicating Se- quential Processes (CSP) [1, 2], a new programming model for dealing with parallelism and concurrency that has a strong mathematical basis. Supported by a range of direct implemen- tation technologies, CSP avoids most of the fundamental problems inherent in concurrent design – allowing it to be used with confidence by systems engineers with only a modest amount of training and no specialist mathematical knowledge. Despite this, no mainstream operating systems or programming languages have built- in support for CSP mechanisms. For concurrency, they offer only unstructured varieties of threads and optional locking mechanisms (such as semaphores or monitors). They provide no support to enforce correct and efficient use of those locks – and cannot be made to provide it. Received wisdom[3] is that this concurrency is hard, should only be used as a last resort (for performance reasons) and only by very experienced designers and programmers. That received wisdom is correct. But CSP turns this around. Of course, occam[4, 5] provides the standard for CSP implementation against which oth- ers must be measured – but occam is not (yet) a mainstream language. For C, CCSP[6] is a library and run-time kernel that provides the occam model. JCSP[7] and CTJ[8] are CSP/occam libraries for Java. This paper reports on C++CSP: a CSP library for C++ that combines an Object Oriented API (derived from JCSP, but with modifications to take advan- tage of specific C++ capabilities, such as templates) with fast kernel support (along the lines of CCSP and occam). C++CSP runs native under either Windows or Linux/Unix. Applications, therefore, have direct access to all standard Windows – or Linux/Unix – libraries. This paper provides a user’s introduction to the library, describes some of the internal workings and provides early performance figures. It assumes readers have familiarity with the basic ideas and mechanisms of CSP, occam, JCSP and C++. 140 N.C.C. Brown and P.H. Welch / An Introduction to the Kent C++CSP Library 2 Library Details At the heart of the CSP paradigm are processes and channels – processes being pieces of code that can be executed in sequence or in parallel and channels being the means by which they communicate. Like JCSP before it, C++CSP adopts an object-oriented approach to implementing CSP. A process is a subclass of CSProcess, and channels are classes, such as the standard one-to- one unbuffered channel One2OneChannel. Channels are templated classes (the mechanism for generic programming in C++) that can be used to communicate any assignable type, be it a primitive, a “pod” class or a more complex class. In a typical scenario, a parent process creates a channel and passes a reading end (also a class – Chanin) to one process and a writing end (again, a class – Chanout) to another process. That way, neither child process can access the channel directly to try and obtain a class representing the opposite end of the channel. As in JCSP, a new process is implemented by declaring a new class as a child of the CSProcess class and implementing the void run() method (though in C++CSP this is protected rather than public1). Unfortunately, it is necessary to pass to the constructor of CSProcess the size of the stack needed for the process. This will be explained later. The C++CSP library provides: • processes (run either in sequence or in parallel); • channels (either or both of the reading and writing ends may be shared; also, they may be buffered using a variety of library or user-defined buffers); • parallel channel communications (a special case of parallelism included for conve- nience); • ALTernatives; • buckets and barriers[9]; • mobile objects with the same semantics as their (modern) occam counterparts; • easy and secure channel poisoning for clean shutdown; • support for Microsoft Windows (98 and later); • support for Linux and most other Unix-variants. 3 Tutorial 3.1 The Semantics of Assignment and Communication Channel communication is just a distributed form of assignment – a value is computed in one process and assigned to a variable in another (after synchronising the two processes of course). In occam, there is the equivalence: FOO x, y: FOO x, y: ... ... x := y equals CHAN FOO c: PAR c!y c?x 1This means that processes can only be run by the library itself and cannot be run directly by the user, due to problems with stacks that will be explored later in section 4.2. N.C.C. Brown and P.H. Welch / An Introduction to the Kent C++CSP Library 141 Therefore, the semantics of communication must be compatible with the semantics of assignment. In C++, the meaning of the assignment operator, =, can be overridden to mean whatever the programmer wishes it to mean... and this will be reflected in the meaning of communica- tion in the C++CSP library. So, if a class overrides assignment to mean “shallow copying”, a shallow copy of an object will be sent across a C++CSP channel. If a class has not over- ridden its assignment operator, then a “member-wise” copy (the default for assignment of C++ objects) is received by the reading process. If the channel carries array types, only the pointers will be communicated, since in C++ an array is treated as a pointer. If the channel carries primitive types (int, float etc.), only their values will be communicated. In this paper, most of the examples work with int-carrying channels. If Bar is a class, then Bar-carrying channels are handled with equal ease - examples are referred to in Sections 5.3 and 6.3. 3.2 Our First Program We will now look at creating a simple program using the C++CSP library. There will be a writer process that writes 100 integers to a channel then exits, and a reader process that reads 100 integers from a channel and exits. These processes are declared as follows2: class Writer : public CSProcess { private: Chanout<int> out; //writing end of the channel protected: virtual void run(); //overrides the method in CSProcess public: Writer(const Chanout<int>& o); //constructor }; class Reader : public CSProcess { private: Chanin<int> in; //reading end of the channel protected: virtual void run(); //overrides the method in CSProcess public: Reader(const Chanin<int>& i); //constructor }; The constructors are as follows (we will use an arbitrarily-sized large stack): Writer::Writer(const Chanout<int>& o) : CSProcess(65536),out(o) { } Reader::Reader(const Chanin<int>& i) : CSProcess(65536),in(i) { } The above pieces of code are a general template for any process. Each process is a child of CSProcess and must implement the run method. They will have as class members 2In all sample code, it is assumed that the namespace of the library, csp, is in scope. 142 N.C.C. Brown and P.H. Welch / An Introduction to the Kent C++CSP Library any channel ends they require; these are passed to the class constructor. As can be seen above, channel ends can be assigned for ease of use. Following the object-oriented paradigm, channel ends are the same regardless of what type of channel (buffered, shared, or both) they are attached to, allowing any channel type to be used with any process (bar a few exceptions regarding ALTernatives and shared channels).
Load more

Recommended publications
  • Life of Occam-Pi
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Kent Academic Repository Communicating Process Architectures 2013 293 P.H. Welch et al. (Eds.) Open Channel Publishing Ltd., 2013 © 2013 The authors and Open Channel Publishing Ltd. All rights reserved. Life of occam-Pi Peter H. WELCH School of Computing, University of Kent, UK [email protected] Abstract. This paper considers some questions prompted by a brief review of the history of computing. Why is programming so hard? Why is concurrency considered an “advanced” subject? What’s the matter with Objects? Where did all the Maths go? In searching for answers, the paper looks at some concerns over fundamental ideas within object orientation (as represented by modern programming languages), before focussing on the concurrency model of communicating processes and its particular expression in the occam family of languages. In that focus, it looks at the history of occam, its underlying philosophy (Ockham’s Razor), its semantic foundation on Hoare’s CSP, its principles of process oriented design and its development over almost three decades into occam-π (which blends in the concurrency dynamics of Milner’s π-calculus). Also presented will be an urgent need for rationalisation – occam-π is an experiment that has demonstrated significant results, but now needs time to be spent on careful review and implementing the conclusions of that review. Finally, the future is considered. In particular, is there a future? Keywords. process, object, local reasoning, global reasoning, occam-pi, concurrency, compositionality, verification, multicore, efficiency, scalability, safety, simplicity Introduction Let’s try a few questions to which the answer might be: “occam, obviously”.
    [Show full text]
  • Rmox: a Raw-Metal Occam Experiment
    Communicating Process Architectures – 2003 269 Jan F. Broenink and Gerald H. Hilderink (Eds.) IOS Press, 2003 RMoX: A Raw-Metal occam Experiment Fred BARNES†, Christian JACOBSEN† and Brian VINTER‡ † Computing Laboratory, University of Kent, Canterbury, Kent, CT2 7NF, England. {frmb2,clj3}@kent.ac.uk ‡ Department of Mathematics and Computer Science, University of Southern Denmark, Odense, Denmark. [email protected] Abstract. Operating-systems are the core software component of many modern com- puter systems, ranging from small specialised embedded systems through to large distributed operating-systems. This paper presents RMoX: a highly concurrent CSP- based operating-system written in occam. The motivation for this stems from the overwhelming need for reliable, secure and scalable operating-systems. The major- ity of operating-systems are written in C, a language that easily offers the level of flexibility required (for example, interfacing with assembly routines). C compilers, however, provide little or no mechanism to guard against race-hazard and aliasing er- rors, that can lead to catastrophic run-time failure (as well as to more subtle errors, such as security loop-holes). The RMoX operating-system presents a novel approach to operating-system design (although this is not the first CSP-based operating-system). Concurrency is utilised at all levels, resulting in a system design that is well defined, easily understood and scalable. The implementation, using the KRoC extended oc- cam, provides guarantees of freedom from race-hazard and aliasing errors, and makes extensive use of the recently added support for dynamic process creation and channel mobility. Whilst targeted at mainstream computing, the ideas and methods presented are equally applicable for small-scale embedded systems — where advantage can be made of the lightweight nature of RMoX (providing fast interrupt responses, for ex- ample).
    [Show full text]
  • Chapters 1-10 As a Single File (Pdf)
    Boldrin & Levine: Against Intellectual Monopoly, Chapter 1 Chapter 1: Introduction In late 1764, while repairing a small Newcomen steam engine, the idea of allowing steam to expand and condense in separate containers sprang into the mind of James Watt. He spent the next few months in unceasing labor building a model of the new engine. In 1768, after a series of improvements and substantial borrowing, he applied for a patent on the idea. August found Watt in London about the patent and he spent another six months working hard to obtain it. The patent was finally awarded in January of the following year. Nothing much happened by way of production until 1775. Then, with a major effort supported by his business partner, the rich industrialist Matthew Boulton, Watt secured an Act of Parliament extending his patent until the year 1800. The great statesman Edmund Burke spoke eloquently in Parliament in the name of economic freedom and against the creation of unnecessary monopoly – but to no avail. The connections of Watt’s partner Boulton were too solid to be defeated by simple principle. Once Watt’s patents were secured and production started, a substantial portion of his energy was devoted to fending off rival inventors. In 1782, Watt secured an additional patent, made “necessary in consequence of ... having been so unfairly anticipated, by [Matthew] Wasborough in the crank motion.” More dramatically, in the 1790s, when the superior Hornblower engine was put into production, Boulton and Watt went after him with the full force of the legal system. During the period of Watt’s patents the U.K.
    [Show full text]
  • Modelling with Cellular Automata: Problem Solving Environments and Multidimensional Applications
    UvA-DARE (Digital Academic Repository) Modelling with cellular automata: problem solving environments and multidimensional applications Naumov, L.A. Publication date 2011 Document Version Final published version Link to publication Citation for published version (APA): Naumov, L. A. (2011). Modelling with cellular automata: problem solving environments and multidimensional applications. General rights It is not permitted to download or to forward/distribute the text or part of it without the consent of the author(s) and/or copyright holder(s), other than for strictly personal, individual use, unless the work is under an open content license (like Creative Commons). Disclaimer/Complaints regulations If you believe that digital publication of certain material infringes any of your rights or (privacy) interests, please let the Library know, stating your reasons. In case of a legitimate complaint, the Library will make the material inaccessible and/or remove it from the website. Please Ask the Library: https://uba.uva.nl/en/contact, or a letter to: Library of the University of Amsterdam, Secretariat, Singel 425, 1012 WP Amsterdam, The Netherlands. You will be contacted as soon as possible. UvA-DARE is a service provided by the library of the University of Amsterdam (https://dare.uva.nl) Download date:05 Oct 2021 Modelling with Cellular Automata: Problem Solving Environments and Multidimensional Applications ACADEMISCH PROEFSCHRIFT ter verkrijging van de graad van doctor aan de Universiteit van Amsterdam op gezag van de Rector Magnificus prof. dr. D.C. van den Boom ten overstaan van een door het college voor promoties ingestelde commissie, in het openbaar te verdedigen in de Agnietenkapel op dinsdag 14 juni 2011, te 10:00 uur door Lev Alexandrovich Naumov geboren te Sint-Petersburg, Rusland Promotiecommissie Promotor: Prof.
    [Show full text]
  • Implementation of Kroc on Analog Devices' "SHARC"
    Proceedings of the 19 WoTUG Technical Meeting, 31 March- 3 April 1996, Nottingham, UK 179 Implementation of KRoC on Analog Devices’ "SHARC" DSP G.W. Otten, M.H. Schwirtz, R. Bruis, J.F Broenink and A.W.P. Bakkers Mechatronic Research Centre Twente and Control Laboratory, Department of Electrical Engineering, University of Twente, PO Box 217, 7500 AE Enschede, The Netherlands. Email: [email protected] Abstract: This paper summarises the experiences gained at the Control Laboratory of the University of Twente in porting the Kent Retargetable occam Compiler - KroC - to the Analog Devices’ ADSP21060 SHARC Digital Signal Processor. The choice of porting the KRoC to the DSP processor was in our view both a challenge and an absolute necessity because DSP processors are an important ingredient in modern day control systems. Currently, our implementation contains the most important occam primitives such as channel communication, PAR, ALT, and most of the integer arithmatic. Furthermore, a basic kernel was realised, providing channel- communication based scheduling only. This porting process, using quite straight- forward modifications of the SPARC KRoC-translator, was done within six weeks. A representative benchmark was constructed, showing that the 33Mhz SHARC-KRoC implementation is 40% faster than the the 25Mhz T800 using the INMOS D7205 Toolset. 1. Introduction Prospective control system design will inevitably be influenced by present day micro-processor developments. These developments are in brief: availability of (Digital Signal) Processors with built-in memory and equipped with external communication channels and a general trend in the development of micro processors with combined DRAM+CPU together with on-chip integrated fibre optic link drivers.
    [Show full text]
  • Rmox: a Raw-Metal Occam Experiment
    Communicating Process Architectures – 2003 269 Jan F. Broenink (Eds.) IOS Press, 2003 RMoX: A Raw-Metal occam Experiment Fred BARNES†, Christian JACOBSEN† and Brian VINTER‡ † Computing Laboratory, University of Kent, Canterbury, Kent, CT2 7NF, England. {frmb2,clj3}@kent.ac.uk ‡ Department of Mathematics and Computer Science, University of Southern Denmark, Odense, Denmark. [email protected] Abstract. Operating-systems are the core software component of many modern com- puter systems, ranging from small specialised embedded systems through to large distributed operating-systems. This paper presents RMoX: a highly concurrent CSP- based operating-system written in occam. The motivation for this stems from the overwhelming need for reliable, secure and scalable operating-systems. The major- ity of operating-systems are written in C, a language that easily offers the level of flexibility required (for example, interfacing with assembly routines). C compilers, however, provide little or no mechanism to guard against race-hazard and aliasing er- rors, that can lead to catastrophic run-time failure (as well as to more subtle errors, such as security loop-holes). The RMoX operating-system presents a novel approach to operating-system design (although this is not the first CSP-based operating-system). Concurrency is utilised at all levels, resulting in a system design that is well defined, easily understood and scalable. The implementation, using the KRoC extended oc- cam, provides guarantees of freedom from race-hazard and aliasing errors, and makes extensive use of the recently added support for dynamic process creation and channel mobility. Whilst targeted at mainstream computing, the ideas and methods presented are equally applicable for small-scale embedded systems — where advantage can be made of the lightweight nature of RMoX (providing fast interrupt responses, for ex- ample).
    [Show full text]
  • Synchronous Distributed Behaviours Using Occam
    Chapter 3 Synchronous distributed behaviours using Occam At this point, the installation of kroc, the Kent Research Occam Compiler should be con- sidered. The first section will detail how to proceed on a Linux installation. 3.1 Installing kroc The Occam compiler is developed at University of Kent, with its home page at http://projects.cs.kent.ac.uk/projects/kroc/trac/.. Two branches are proposed: out of the same compiler frontend: kroc i386 compiler which makes use of a code generator for x86, thus enabling • execution of programs on current multi-cores, Transterpreter Virtual Machine (TVM), which enables execution on micro-controllers. • The two branches are good targets for wireless sensor designs. The first is used to support concurrent simulation of networks, the second will support execution at sensor level in a portable way. In this chapter, the i386 execution of simulations is the main concern, and our guide is the web page provided by Kent (it would be sufficient to follow these steps). This section is just a check out of instructions provided at this location. 1. access installation page from /sl Information for users 2. check your system uname -a Linux MyLinuxBox 3.2.0-51-generic #77-Ubuntu SMP Wed Jul 24 20:18:19 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux I have a 64bits installation supporting concurrent execution. lsb_release -a LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch Distributor ID: Ubuntu Description: Ubuntu 12.04.2 LTS Release: 12.04 Codename: precise This is Precise 12.04 LTS distribution of Ubuntu.
    [Show full text]
  • A Cell Transterpreter
    CORE Metadata, citation and similar papers at core.ac.uk Provided by Kent Academic Repository Communicating Process Architectures 2006 215 Peter Welch, Jon Kerridge, and Fred Barnes (Eds.) IOS Press, 2006 A Cell Transterpreter Damian J. DIMMICH, Christian L. JACOBSEN, Matthew C. JADUD Computing Laboratory, University of Kent, Canterbury, CT2 7NF, UK. {djd20 , clj3 , mcj4} @kent.ac.uk Abstract. The Cell Broadband Engine is a hybrid processor which consists of a Pow- erPC core and eight vector co-processors on a single die. Its unique design poses a number of language design and implementation challenges. To begin exploring these challenges, we have ported the Transterpreter to the Cell Broadband Engine. The Transterpreter is a small, portable runtime for concurrent languages and can be used as a platform for experimenting with language concepts. This paper describes a pre- liminary attempt at porting the Transterpreter runtime to the Cell Broadband Engine and explores ways to program it using a concurrent language. Keywords. CELL processor, Transterpreter, Portable run-time environments Introduction Multi-core processors are becoming commonplace in desktop computers, laptops and games consoles [Rat05,BDK+05,KAO05]. Traditionally programming such concurrent systems has been considered difficult [Lee06,Boe05]. We believe that creating and designing software that makes use of concurrency provided by hardware can be easy, given a language and runtime that provide support for concurrency. With a compiler that can check for certain errors in concurrent code, and a runtime that gracefully reports error conditions surrounding program deadlock, developing such software can become simpler. The Sony PlayStation III [Son06], a consumer games console which will be released at the end of 2006, is an example of a readily available and affordable multi-core system.
    [Show full text]
  • Native Code Generation Using the Transterpreter
    Communicating Process Architectures 2006 269 Peter Welch, Jon Kerridge, and Fred Barnes (Eds.) IOS Press, 2006 Native Code Generation Using the Transterpreter Christian L. JACOBSEN, Damian J. DIMMICH and Matthew C. JADUD Computing Laboratory, University of Kent, Canterbury, Kent, CT2 7NZ, England. {clj3 , djd20 , mcj4} @kent.ac.uk Abstract. We are interested in languages that provide powerful abstractions for con- currency and parallelism that execute everywhere, efficiently. Currently, the existing runtime environments for the occam-π programming language provide either one of these features (portability) or some semblance of the other (performance). We believe that both can be achieved through the careful generation of C from occam-π, and demonstrate that this is possible using the Transterpreter, a portable interpreter for occam-π, as our starting point. Keywords. Transterpreter, native code, GCC, occam-π Introduction The Transterpreter [1] is a virtual machine for CSP [2] and Pi-calculus [3] based languages. Intended as a platform for concurrent language design and research, it also fully supports the execution of programs written in the occam-π [4] language. To support our research goals, the Transterpreter was designed to be extensible and portable. This does mean that it is unlikely to be able to achieve the level of performance that could be obtained by compiling directly to native code. However, what the Transterpreter lacks in performance, it possesses in portability, and has enabled the execution of occam-π on platforms as diverse as the Mac OS X (PowerPC) and the LEGO Mindstorms (H8/300) [5]. Porting the Transterpreter to a POSIX compliant OS, such as Mac OS X, is no harder than recompiling 4000 lines of ANSI C.
    [Show full text]
  • Rmox – a Raw Metal Occam Experiment 1/30
    RMoX { A Raw Metal occam Experiment 1/30 RMoX: A Raw Metal occam Experiment Fred Barnes† ([email protected]) Christian Jacobsen† ([email protected]) Brian Vinter‡ ([email protected]) † Computing Laboratory, University of Kent ‡ Department of Maths and Computer Science, University of Southern Denmark RMoX { A Raw Metal occam Experiment 2/30 Contents • Introduction • Dynamic occam • Design: { the `kernel' { device drivers { ¯lesystems { networking { top-level and console • Implementation: { accessing hardware { real and user-mode RMoX • Conclusions RMoX { A Raw Metal occam Experiment 3/30 Motivation • Do we really need another OS ? • Most existing operating systems su®er: { from software error { from high overheads { a lack of scalability • We want an operating system that: { has a rigorous design { is free from software error { is fast! RMoX { A Raw Metal occam Experiment 4/30 Introduction • Raw Metal occam: { runs on the \raw" hardware { with some help from the UTAH Flux OSKit { and a modi¯ed KRoC run-time system • CSP design • Dynamic occam implementation RMoX { A Raw Metal occam Experiment 5/30 Dynamic occam RMoX extensively uses two of the new dynamic features of KRoC/occam: • mobile channel-bundle ends • dynamic process creation (fork) These support: • dynamic network expansion and re-con¯guration • scalable server farms RMoX { A Raw Metal occam Experiment 6/30 Mobile Data • Provides a movement semantics for assign- ment and communication • Implementation supports both static and dynamic mobiles • Unit-time assignment and communication
    [Show full text]
  • Download Programs to the LEGO As Well As Enable Line-Of-Sight Communi- Cation Between Robots
    Kent Academic Repository Full text document (pdf) Citation for published version Jacobsen, Christian L. and Jadud, Matthew C. (2004) The Transterpreter: A Transputer Interpreter. In: East, Ian R. and Duce, David and Green, Mark and Martin, Jeremy and Welch, Peter H., eds. Communicating Process Architectures 2004. Concurrent Systems Engineering Series, 62. IOS Press, Amsterdam pp. 99-106. ISBN 1-58603-458-8. DOI Link to record in KAR https://kar.kent.ac.uk/14104/ Document Version UNSPECIFIED Copyright & reuse Content in the Kent Academic Repository is made available for research purposes. Unless otherwise stated all content is protected by copyright and in the absence of an open licence (eg Creative Commons), permissions for further reuse of content should be sought from the publisher, author or other copyright holder. Versions of research The version in the Kent Academic Repository may differ from the final published version. Users are advised to check http://kar.kent.ac.uk for the status of the paper. Users should always cite the published version of record. Enquiries For any further enquiries regarding the licence status of this document, please contact: [email protected] If you believe this document infringes copyright then please contact the KAR admin team with the take-down information provided at http://kar.kent.ac.uk/contact.html Communicating Process Architectures 2004 99 Ian East, Jeremy Martin, Peter Welch, David Duce, and Mark Green (Eds.) IOS Press, 2004 The Transterpreter: A Transputer Interpreter Christian L. JACOBSEN [email protected] Matthew C. JADUD [email protected] Computing Laboratory, University of Kent, Canterbury, CT2 7NF, UK Abstract.
    [Show full text]
  • Communicating Mobile Processes: Introducing Occam-Pi
    Communicating Mobile Processes Introducing occam-pi Peter H. Welch and Frederick R.M. Barnes Computing Laboratory, University of Kent, Canterbury, Kent, CT2 7NF, England. {P.H.Welch,F.R.M.Barnes}@kent.ac.uk Abstract. This paper introduces occam-π, an efficient and safe binding of key elements from Hoare’s CSP and Milner’s π-calculus into a pro- gramming language of industrial strength. A brief overview of classical occam is presented, before focussing on the extensions providing data, channel and process mobility. Some implementation details are given, along with current benchmark results. Application techniques exploiting mobile processes for the direct modelling of large-scale natural systems are outlined, including the modelling of locality (so that free-ranging pro- cesses can locate each other). Run-time overheads are sufficiently low so that systems comprising millions of dynamically assembling and commu- nicating processes are practical on modest processor resources. The ideas and technology will scale further to address larger systems of arbitrary complexity, distributed over multiple processors with no semantic discon- tinuity. Semantic design, comprehension and analysis are made possible through a natural structuring of systems into multiple levels of network and the compositionality of the underlying algebra. 1 Introduction 1.1 Mobile Processes in occam-π A process, embedded anywhere in a dynamically evolving network, may suspend itself mid-execution, be safely disconnected from its local environment, moved (by communication along a channel), reconnected to a new environment and reactivated. Upon reactivation, the process resumes execution from the same state (i.e. data values and code positions) it held when it suspended.
    [Show full text]