Quantum field by Ciro Santilli 37 Updated +Created
x86 Paging Tutorial / TLB replacement policy by Ciro Santilli 37 Updated +Created
When TLB is filled up, older addresses are overwritten. Just like CPU cache, the replacement policy is a potentially complex operation, but a simple and reasonable heuristic is to remove the least recently used entry (LRU).
With LRU, starting from state:
  valid  linear  physical
  -----  ------  --------
> 1      00003   00005
  1      00007   00009
  1      00009   00001
  1      0000B   00003
adding 0000D -> 0000A would give:
  valid  linear  physical
  -----  ------  --------
  1      0000D   0000A
> 1      00007   00009
  1      00009   00001
  1      0000B   00003
x86 Paging Tutorial / CAM by Ciro Santilli 37 Updated +Created
Using the TLB makes translation faster, because the initial translation takes one access per TLB level, which means 2 on a simple 32 bit scheme, but 3 or 4 on 64 bit architectures.
The TLB is usually implemented as an expensive type of RAM called content-addressable memory (CAM). CAM implements an associative map on hardware, that is, a structure that given a key (linear address), retrieves a value.
Mappings could also be implemented on RAM addresses, but CAM mappings may required much less entries than a RAM mapping.
For example, a map in which:
  • both keys and values have 20 bits (the case of a simple paging schemes)
  • at most 4 values need to be stored at each time
could be stored in a TLB with 4 entries:
linear  physical
------  --------
00000   00001
00001   00010
00010   00011
FFFFF   00000
However, to implement this with RAM, it would be necessary to have 2^20 addresses:
linear  physical
------  --------
00000   00001
00001   00010
00010   00011
... (from 00011 to FFFFE)
FFFFF   00000
which would be even more expensive than using a TLB.
Secure Shell by Ciro Santilli 37 Updated +Created
Ciro Santilli's hardware / Liv Flourish 2 (2018) by Ciro Santilli 37 Updated +Created
2022: saddle and seat post stolen near home. Burn in Hell, motherfuckers. Bought a seatpost marked SP342 MICROPOST ALLOY 3 30.4mm. Like this: web.archive.org/web/20220208115055/https://www.ebay.co.uk/itm/Lightweight-Alloy-Micropost-Bike-MTB-Seatpost-25-4mm-Seat-Pin-300m-Long-Silver-/402311713393 but 30.4mm. OK, bought the Park Tool PW-5 15mm pedal wrench tool. Wasn't expensive at all.
TODO understand other markings on receipt: "18 Flourish FS W Sil XS".
The exact specs pages is lost forever. Closest one we've got is the 2020: web.archive.org/web/20200927204537/https://www.liv-cycling.com/gb/flourish-2
Frame: size: XS. Marking near bottom bracket: F/N GY17Z1327 DK: WGI GY17Z1327 F ES:BI-2339.
Seatpost: TODO diameter. Measured in store 30.4mm after original stolen, although 2020 says 30.9. 30.4mm seemed to fit OK, and measuring with ruler gives 30.5/30.6, I don't think a 30.9 can possibly fit.
Saddle: Liv Contact Comfort Plus Saddle, color golden brown. Same as this but blown: www.liv-cycling.com/gb/contact-comfort-plus-saddle-liv Actual color:
https://raw.githubusercontent.com/cirosantilli/media/master/Liv_contact_comfort_plus_2018.jpg
Modulo operation by Ciro Santilli 37 Updated +Created

Pinned article: ourbigbook/introduction-to-the-ourbigbook-project

Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
We have two killer features:
  1. topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculus
    Articles of different users are sorted by upvote within each article page. This feature is a bit like:
    • a Wikipedia where each user can have their own version of each article
    • a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
    This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.
    Figure 1.
    Screenshot of the "Derivative" topic page
    . View it live at: ourbigbook.com/go/topic/derivative
  2. local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:
    This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
    Figure 5. . You can also edit articles on the Web editor without installing anything locally.
    Video 3.
    Edit locally and publish demo
    . Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension.
  3. https://raw.githubusercontent.com/ourbigbook/ourbigbook-media/master/feature/x/hilbert-space-arrow.png
  4. Infinitely deep tables of contents:
    Figure 6.
    Dynamic article tree with infinitely deep table of contents
    .
    Descendant pages can also show up as toplevel e.g.: ourbigbook.com/cirosantilli/chordate-subclade
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact