• 6 Posts
  • 39 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle







  • The FS feature is great, it’s just cumbersome to use without a tool.

    Snapper works well for a local backup like history both against botched updates and accidental deletion, but eats up the free space with the default settings.

    Timeshift is an easy to use GUI but doesn’t support non-default partitions.

    Also the quota support had a nasty side effect: freezing the whole system on snapshot deletion.


  • It’s hard to live up to expectations after Frieren but here are some that were memorable for me:

    • Fate Zero - it’s a battle royal with magic, the story isn’t the focus but the characters and fights are great
    • Spice and Wolf - this is about a merchant’s journey with an unusual companion (there is a new (re)adaptation coming next season, but the old version is also quite good)
    • A Certain Scientific Railgun - a sci-fi city and it’s secrets, I think it does well in the would building

  • I think calling it a “cache” is not precise. The primary function of the DRAM is to hold the dictionary for translating logical addresses (e.g. sectors) from the OS to the physical addresses (which NAND chip, which bank etc.). This indirection is needed for the controller to do wear leveling without corrupting the filesystem.

    On a SATA SSD without DRAM each read IO could mean 2 actual reads: first the dictionary to find the data and than the actual data being read. As you said HBM helps by eliminating this extra read.

    The read and write caching is just a use of the remaining DRAM capacity. Since modern Operating Systems use the general RAM for the same function it is usually just a small increase to the throughput.










  • Thanks for the links! I updated my config from z3fold to zsmalloc and adjusted the vm.page-cluster to test these out.

    Reading a bit more, I think when using large max_pool_percent (>30) with Zswap the two solutions are more similar than not. A crucial difference is what use-case is more acceptable since Zswap can cause unresponsiveness (and potential lockup) under high memory pressure. While Zram could result in an OOM crash in a similar worst-case scenario.







  • bazsy@lemmy.worldtoLinux@lemmy.mlAMD GPUs are cursed for me
    link
    fedilink
    English
    arrow-up
    2
    ·
    9 months ago

    Most distros use systemd and its logging solution: journald. You can use journalctl to read the logs around the time of the crash for e.g.:

    • journalctl -S -5m this shows the last 5 minutes. Use this when a game crashes but the system continues working and did not reboot.
    • journalctl -b -1 -S -10m this shows the last 10 minutes from the previous boot. Use this if the crash froze the whole system and rebooted.

    Look for red lines (errors) and what wrote them. AMD GPU faults usually have the ‘amdgpu’ mentioned, memory errors could appear as ‘protection fault’.