#asahi · 2022-09-02 08:10
rkjnsnI believe a couple of folks have created live media you can boot via U-Boot after installing the latter via the Asahi installer. Once booted into a live environment, you could theoretically use it to set up your encrypted root and set up the distro of your choice.#asahi · 2022-06-30 21:47
rkjnsnI'm not sure any others have the hardware capability to flip it on/off per process, though.#asahi · 2022-05-17 21:05
rkjnsnYes.#asahi · 2022-04-21 23:06
rkjnsnAh. I use the Matrix bridge myself, so I don't see the [m].#asahi · 2022-04-21 22:46
rkjnsnhttps://matrix.to/#/#_oftc_#asahi:matrix.org#asahi · 2022-04-21 22:45
rkjnsnNot a separate one, but you can join the IRC channel using the OFTC Matrix bridge.#asahi · 2022-03-24 07:30
rkjnsnIf you can get a live media to boot via U-Boot, gparted makes the actual moving / resizing pretty easy.#asahi · 2022-03-18 04:38
rkjnsnI've had builds of Chromium completely lock up my system not infrequently if I have other memory-hungry processes running at the same time. I imagine the watchdog on the M1 would turn that into a reboot.#asahi · 2022-03-12 06:56
rkjnsnirrelevant*#asahi · 2022-03-12 06:56
rkjnsnI know there's https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/25426branch/alpine-source/linux-3.10.x-bsp.txz/download (heh, looks like you're the one who dug it up last year, when I was struggling with btrfs on my NAS), but it sounded like it was pretty much an unusable mess of vendor code with lots of unrelevant whitespace, etc. changes.#asahi · 2022-03-12 06:28
rkjnsnUnless only the bottom 32-bits of the pgoff_t were used for indexing the XArray as chaining or something was used for the rare case of pages exactly 4GiB apart needing to be cached at the same time? As I say, I'm not really familiar with this stuff.#asahi · 2022-03-12 06:28
rkjnsn64-bit pgoff_t would indeed be super useful for my 32-bit NAS, I seem to recall the problem there is it would require changing XArray to be 64-bit on 32-bit platforms, which would be a much wider-reaching change?#asahi · 2022-03-12 06:26
rkjnsnI know that was the motivation for it, but I thought it increased the page size across the board, not just for storage? I can't say I understand this stuff all that well.#asahi · 2022-03-12 03:21
rkjnsn(I gather the idea would then be to get distros to standardize on 16k-page kernels to avoid the 4k performance hit, and on CPUs without hardware 16k support, the kernel would fall back to using 4 4k hardware kernel pages per kernel page? That wouldn't help with things that need 4k pages like FEX though.)#asahi · 2022-03-12 03:16
rkjnsnkov, are you referring to sven's patch? My understanding is that is to support accessing hardware behind a 16k IOMMU while running a 4k kernel on the CPU's 4k page mode. The bootlin patch I linked is to allow running a 16k kernel on a CPU without hardware 16k page support by backing each kernel page with 4 4k hardware pages, which is what I understood agraf to be asking about.#asahi · 2022-03-11 23:46
rkjnsn(I don't think it was dynamic, though. I believe it would always use 4KiB hardware pages even if the hardware supported 16KiB.)#asahi · 2022-03-11 23:39
rkjnsnLooks like it didn't require a huge code change. No idea on the performance impact.#asahi · 2022-03-11 23:38
rkjnsnarnd, agraf: Re 16KiB pages on 4KiB hardware, there was once upon a time a patch developed for 32-bit arm that did just that: https://bootlin.com/blog/large-page-support-for-nas-systems-on-32-bit-arm/#asahi · 2022-02-25 10:33
rkjnsnNow that you mention it, I think I did see in a bug somewhere that the DTK used 16k pages even for Rosetta 2, and support for running Rosetta 2 processes with 4k processes was only available on the final M1 chip. Couldn't say for sure, though.#asahi · 2022-02-25 10:11
rkjnsnRight, flipping the page size on context switch is what I was thinking macOS did, but I seem to recall the consensus being than Linux would probably never support something like that.#asahi · 2022-02-25 10:04
rkjnsnI may be misremembering, but I thought macOS did support processes running with 4k pages for Rosetta 2 even while the kernel and other processes ran with 16k pages.#asahi · 2022-02-25 09:55
rkjnsnClearly we should add support for running the kernel with 16k pages but allowing some user space processes like FEX and Chromium to run with 4k pages. I'm sure that'd be a trivial change that would be easily acceptable upstream, right?#asahi · 2022-02-25 09:43
rkjnsnj“‘’”ey#asahi · 2022-02-19 07:50
rkjnsnF_BARRIERFSYNC was used for fsync instead of doing a flush, it could hopefully ensure that users of fsync would be guaranteed internal consistency of whatever made it to disk, even if there was the possibility for lost writes.#asahi · 2022-02-19 07:50
rkjnsnThat was on macOS using F_BARRIERFSYNC instead of F_FULLFSYNC. If I understand correctly (which it sounds like maybe I don't…), whereas F_FULLFSYNC ensures the data is written to persistent storage F_BARRIERFSYNC, merely ensures that the data written before the sync hits persistent storage before data written after it, but it is still not guaranteed to be written when the call returns. My thinking was that if the underlying functionality used by#asahi · 2022-02-19 07:29
rkjnsnGreat for quickly looking at PDF files that try to force you to download them, as well as viewing files that you know are plain text but the browser doesn't.#asahi · 2022-02-19 07:27
rkjnsnIt lets you open any browser-supported file in the browser itself, regardless of the server-sent mime type or content disposition.#asahi · 2022-02-19 07:27
rkjnsntpw_rules, if you use Firefox, I have found this extension to be eminently useful: https://addons.mozilla.org/firefox/addon/open-in-browser/