Skip to content
  • RTLinux

    Some old stuff I found in the office

    June 10, 2016
  • Synchronous processors

    Imagine a processor with no interrupts. We can do a lot better and get rid of most exceptions (e.g. system calls, page faults etc.), most peripheral devices/buses, and even cache misses, but let’s start with interrupts. Modern micro-processors are bloated with circuitry that is designed to allow the precious CPU to switch back and forth…

    May 11, 2016
  • IEEE 1588 PTP is a mess

    IEEE 1588 was not designed for modern enterprise computer networks and contains many hacks to make it sort of work. The standard also suffers from being overly explicit on some things and overly unspecific  on others.  One marker of the flawed process is that IEEE 1588 transparent clocks don’t really comply with Ethernet standards because…

    April 27, 2016
  • MiFID II Clock Sync – talk at Bank of England April 12 2016

    download

    April 18, 2016
  • Operations and maps on finite sequences

    A lot of what I’m trying to do with mathematical models of computer systems involves operations on finite sequences. Define a “finite sequence of length n>0” to be any total map f: {1 … n} → X for some set X. The 0-length sequence is the null map  “nulls”. If f is a finite sequence of…

    March 11, 2016
  • The difference between unspecified, undefined, and non-deterministic

    There is too much confusion in the “formal methods” computer science literature between these three different terms. Let me start with what this means for a state machine and then move on to engineering objects such as threads. Suppose we have a map α: X → Y  where X is the set of finite sequences over X.…

    February 20, 2016
  • Software quality at toyota

    The good stuff starts on page 36 Koopman.   

    February 16, 2016
  • A mathematical basis for understanding software modularity

    Download.

    February 9, 2016
  • one way queues

    Here’s some code for lock free queues for a single producer and single consumer. The code is designed for Intel multiprocessors with strong memory model. I don’t know what ARM offers these days. But the strong memory model for x86 means that the program doesn’t need any special synchronizing operations at all. All it needs…

    February 6, 2016
  • The Auragen file system.

    This article on the interesting Wave Transactional File System inspired me to look up an earlier file system that also used copy on write semantics. From: Anita Borg, Wolfgang Blau, Wolfgang Graetsch, Ferdinand Herrmann, and Wolfgang Oberle. 1989. Fault tolerance under UNIX. ACM Trans. Comput. Syst. 7, 1 (January 1989), 1-24. DOI=http://dx.doi.org/10.1145/58564.58565   4.3 Availability…

    January 25, 2016
←Previous Page
1 … 6 7 8 9 10 … 45
Next Page→

keeping simple

    • Groundbreaking treatise on state machines, paxos, specification
    • The RTLinux patent 5,995,745
    • Notes on Security and Common Criteria
    • Download code

keeping simple

Proudly powered by WordPress