blashork [she/her]

  • 0 Posts
  • 20 Comments
Joined 2 years ago
cake
Cake day: April 8th, 2022

help-circle



  • This is speculation:

    I think a lot of it is temporarily leased or loaned. i was watching a retrobytws video recently, cant remember the exact name. but it was about this console that was ‘designed for girls’ (read what old men in suits think teenage girls want). He said a lot of.yputubers have made videos on it, but console is actually pretty rare. One or two people own pne amd loan it out to others for their videos.

    Also auctioning. I gotta imagine some of it can be flipped.

    Maybe donated to a museum.

    That’s just me speculatong tho.





  • I’m well aware. While I don’t personally work on the gpu related stuff, I do work at a company that has to do a lot of gpu computing. My opinions on this topic are mostly informed by coworkers who do write gpu code, specifically a lot of opencl kernels. opencl has a lot of shortcomings and issues, and the kernel model is a bitch to work with. However, that isn’t the point. The point is about compatibility. You can have a really good gpu but if you don’t have adversarial compatibility with your competitors, it will just die. Specifically, amd have done a shit job at making cuda run on amd gpus. rocm is a disjointed mess, it sucked when I had to work with it in uni, it still sucks now. Cuda is bad and proprietary, but any modern gpu should still be able to run cuda crap simply because it’s useful to be able to do so, and there’s a lot of things already built with it that should remain accessible.

    The fact that amd have not been able to get a component as critical as their adversarial compatibility layer working while Moore has already implemented it for their early generation of cards shows:

    • how profound the failures of amd and western computing companies is
    • the breakneck pace and incredible technical achievements of chinese gpu development





  • bcache is inherently designed to be an ssd cache that sits in front of slower bigger disks. Bcachefs is an extension of this into it’s own filesystem. iirc the words of the bcache creator were: ‘we’ve implemented 80% of a filesystem here, might as well go the rest of the way’. So how much it thrashes a disk is based on what position you give it in the architecture. The caching ssds are going to be used heavily, taking advantage of their fast random access to manage all random accesses, while sequential operations generally go to the slower disk that’s set as the background device. The background disks will tend to be accessed less.

    So yeah, it’s based on what kind of disk and position in the bcache, and what caching options you enable. If you want to look into it further, bcache is fs agnostic, so if you can find some tests that have been done for bcache enabled for classic linux filesystems, like ext4 and xfs, that include hardware degradation info, you’ll probably end up with similar usage and hardware wear with the actual bcachefs.





  • I have made a python script and ran it on a clone of your git repo to confirm it works, simply run it at the root directory of wherever the files are, it will walk through and find module.json and do the replace.

    #!/usr/bin/env python3
    
    import re
    import os
    
    import fileinput
    
    pattern = re.compile(r'(?P\.+)\"compatibility\":{\"minimum\":\"(?P\\d+)\",\"verified\":\"(?P\\d+)\"},(?P\.+)')
    
    def make11(match):
        if match.groupdict().get('min', None) and match.groupdict().get('ver', None):
            return f"{match.groupdict()['pre']}\"compatibility\":{{\"minimum\":\"11\",\"verified\":\"11\"}},{match.groupdict()['post']}"
    
    for root, dirs, files in os.walk("."):
        for file in files:
            if file == "module.json":
                for line in fileinput.input(f"{root}/{file}", inplace=True):
                    print(re.sub(pattern, make11, line))
    

    edit: lemmy is fucking with the formatting and removing the fucking regex group names, which will bork it. I’ve tried fixing it, dm me if you want me to send a downloadable link to the script




  • blashork [she/her]@hexbear.nettoLinux@lemmy.mlbtrfs appreciation post
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    3
    ·
    1 year ago

    I’m glad it’ working well for you, but I don’t think it’ true to say that btrfs gets beyond its fair share of flak. It gets the exactly correct amount of flak for what it is. Every place I have worked at that wanted to deploy a COW fs on like, a NAS or server, has always gone with zfs. btrfs is such a mess it never even enters the conversation. Even if it can have its bugs ironed out, the bcache dev was right in pointing out that its on disk formats are poorly designed for their job, and cannot be revised except in a new version of the entire fs. I hope bcachefs gets merged into the kernel next year, that’s a filesystem I would actually trust with my data.