home.social

#telix — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #telix, aggregated by home.social.

fetched live
  1. In Onur Mutlus Vorlesung wurde heute die TLB-Reichweite nicht erwähnt. Angesichts dessen verfehlt Intels TLB-Design den Zweck von Superpages, weil seine TLB-Reichweite in Stein gemeißelt ist. Deswegen ist diese Auslassung so wesentlich.

    In Onur Mutlu's lecture today, TLB reach wasn't mentioned. Intel's TLB design defeats the entire point of superpages in light of that because its TLB reach is set in stone, and that's why the omission is so glaring.

    #superpages #TLB #Telix

  2. For evaluation strategies, I see:
    - 1. TLB-MPKI Talluri-Hill (ASPLOS '94), Navarro-Iyer-Druschel-Cox (OSDI '02), Barr-Cox-Rixner (ISCA '10)
    - 2. cache pollution, maybe LLC-MPKI, originators unclear
    - 3. LLC/TLB-MPKI vs. RAM scaling curves to determine „memory walls” per Wulf-McKee '95
    - 4. Attribution / stack-distance modelling per Mattson '70

    My own list of things I'd like to measure is:
    - 1. Queueing: inter-arrival times and service times have more predictive power
    - 2. Distribution fairness: the grand total never matters as much as the distribution, where fairness is a central concern, as well as priority inversion
    - 3. Distribution utilisation: is effective use being made of sizes across the size spectrum?
    - 4. Verification of small superpage size allocation guarantees
    - 5. Fragmentation metrics
    - 6. Verification of increased allocation success likelihoods for larger page sizes in the face of external fragmentation
    - 7. Defragmentation overhead
    - 8. Distribution to shared mappings: the highest impact can be had via sharing, so it's also a question of whether the contiguity has been distributed to the shared memory objects of greatest impact.

    The MPKI notion is on the one hand a reciprocal of inter-arrival times and on the other isn't naturally comparable or extensible to service times. Wulf-McKee recast in queueing theoretical terms still doesn't cover the full range of issues I'm working on, though. Metrics for 4. distribution fairness, 7. defragmentation overhead and 8. distribution to shared mappings and maybe more need to be devised.

    #telix #pgcl #superpages

  3. Never mind just Linux; this would seem to raise serious issues for any group producing their own kernel without an army of lawyers on staff e.g. *BSD, RedoxOS, Graphene, ReactOS, Haiku, illumos and perhaps even plan9 and operating system textbooks and learning frameworks like FluxOSKit. There is furthermore some significant scariness about packets crossing borders rendering ppl liable for violations of all this when passing through spaces wherein USA agents may apprehend them.

    youtu.be/SVGw0uY1dsQ

    #telix #Linux #BSD #NetBSD #FreeBSD #OpenBSD #RedoxOS #GrapheneOS #ReactOS #HaikuOS #illumos #plan9 #Hurd #FluxOSKit

  4. My favourite terminal emulator to dial BBSs was cracked Telix for DOS.

    You can still use it today because we added a backend where telephone numbers can be mapped to internet addresses to @DOSBox_Staging.

    en.wikipedia.org/wiki/Telix

    #BBS #RetroComputing #DOS #Telix

  5. @leo and @jeffjarvis got all nostalgic today on #twig (ep 738) about the "days when you bought software in a shrink-wrapped box" and made me climb up into my attic to dig out some relics from my past. We didn't actually wrap #SpySweeper, but the #Telix boxes we stuffed and blow dried ourselves.

  6. So what are people using these days to connect to telnet #BBSes? Back in the day I used to use #Telix. And I recall using Telix in OS/2 with Ray Gwinn's SIO driver to connect to #telnet BBSes during the early 2Ks. Anything that can handle ANSI color?
    #BBS