Computer Science Student @ Imperial
I am currently a student at Imperial College London completing an MSc in "Advanced Computer Science". Previously, I graduated from King's College London with a BSc in Computer Science.
I am particularly interested in the tools we use to build systems that are resilient, secure and fast. I like quite a lot of things. Computer architecture, compilers, operating systems and programming languages (not necessarily in that order). This means, for example, I would be interested in both formalising an ISA and designing hardware to execute it.
If you want a more comprehensive list of skills + experience, consult my CV.
I am always trying to get better at technical writing and hopefully share some interesting stuff while I do it. Each blog entry has a corresponding `.md` file in the same directory, if you prefer reading plaintext.
I describe a lock that is in many regards much faster than an XCHG-based lock for x86 machines. I made this as part of my Master's thesis. I also release my frustrations about computer architecture.
Cache coherence protocols that exist on modern hardware are often proprietary, but this doesn't stop us analysing side channels to figure out how these protocols might be implemented.
A swift and easy guide to Ruby, an old relational HDL for proving the correctness of circuits.
I describe my experience making a machine learning classifier for acute kidney injury (AKI) in pure C. It's interesting because I use a cool technique to compress the data.
How CXL 1.0 and related concepts work.
I work through various known hashtable designs, and also a new one, hoping to see some performance increase.
I work through a derivation for the average number of probes in a hashtable, then try and verify it through real data.
I make a hashtable with SIMD probing for a drag race.
Some of the work I did for a summer research project with one of my very favourite professors. It's quite rare that you get to do 'algorithms research'. I was looking at how we can quickly associate an integer with a specific tree in a nice, ordered way. WARNING: this is one of my first articles I wrote on this website and hence, it's a pretty tough read. Proceed with caution.
I discuss a new idea for safety that I call "item-scoped unsafe code". The idea is to try and get as few things as possible be 'unsafe' and hopefully have everything that is be verifiably safe at runtime.
Email (prefer) | oli.iliffe at gmail.com |
Another Email | oli_iliffe at hotmail.com |