Live data from Hacker News

Linux 7.2

igalia.com

111–120 of 141 posts

Re: Linux 7.2

#111

I just want them to make memory management sane. Is that too much to ask? OOM shouldn't cause a hard reboot. Ok actually I "solved" this by upgrading to 128GB of RAM (before the rampocalypse), but still they should fix it.

Have you considered zram/swap? Since running it, i have never seen mem usage > 95%, even under absurd workloads and have never been oom-killed ever since.

Don't you get slower performance in some cases?

Re: Linux 7.2

#112
post #73

Earlier quoted context omitted.

Strongly disagree. Hardware support improved by leaps and bounds last decade and a half. Namespace isolation and cgroups driven containerization. eBPF appeared and gained adoption. Async I/O (and later just everything async) converged on io_uring. Btrfs is _stable_ - some people believed it would never be possible, ever. All kinds of scheduling were iterated and iterated over. All these things are visible across the…

btrfs is stable?? I used it a couple of years ago and really didn’t have a positive experience. I’ve found ZFS much more stable

It was the default on SUSE / OpenSUSE for years. Haven't used them for a while, not sure whether it still is. No problems with basic functionality including snapshots. I believe some RAID configurations were experimental for long time.

Re: Linux 7.2

#113
post #73

Earlier quoted context omitted.

Strongly disagree. Hardware support improved by leaps and bounds last decade and a half. Namespace isolation and cgroups driven containerization. eBPF appeared and gained adoption. Async I/O (and later just everything async) converged on io_uring. Btrfs is _stable_ - some people believed it would never be possible, ever. All kinds of scheduling were iterated and iterated over. All these things are visible across the…

btrfs is stable?? I used it a couple of years ago and really didn’t have a positive experience. I’ve found ZFS much more stable

Yes. I have used it for 15 years without any problems. Just keep track of snapshots and consumed snapshot space. Besides that, works great!

Re: Linux 7.2

#114

Earlier quoted context omitted.

It's more than that: free and open support for HDMI 2.1 in general. Previously it was only proprietary implementations that didn't leak the spec which were allowed. AMD is just the only one that has really good open source drivers which can benefit from it, and didn't work around the problem by converting HDMI to DisplayPort in a proprietary on-board GPU chip.

Intel only used the converters for 1st gen Arc dGPUs. Battlemage has native HDMI 2.1 and also ran into the same issues as AMD.

Wasn’t it the same with m1 macs, it also had a converter chip and did therefore only support hdmi 2.0.

Re: Linux 7.2

#115
post #68

Earlier quoted context omitted.

Yeah but this is for amdgpu and they had DP2.1 support for a while now.

AMD RX 6700 XT from 2021 only has DP1.4 (but HDMI 2.1). Dell U5226KW from 2026 only has DP1.4 (but HDMI 2.1). I don't think I have seen anything above DP1.4 in the wild for now.

Also interesting is the Steam Machine with its AMD RX 7000 series GPU only has DP1.4 even though those GPUs should be able to do DP2.1

Re: Linux 7.2

#116

I just want them to make memory management sane. Is that too much to ask? OOM shouldn't cause a hard reboot. Ok actually I "solved" this by upgrading to 128GB of RAM (before the rampocalypse), but still they should fix it.

Have you considered zram/swap? Since running it, i have never seen mem usage > 95%, even under absurd workloads and have never been oom-killed ever since.

I did try that back when I only had 32GB. They definitely helped (especially swap) but didn't completely eliminate the problem. I don't know how they do it but I've never had a single issue with OOMs on Windows or Mac. I know Windows doesn't overcommit and it has a proper ctrl-alt-del to let you actually control killing processes if you need to... I'm not sure what Mac does.

Re: Linux 7.2

#117

I just want them to make memory management sane. Is that too much to ask? OOM shouldn't cause a hard reboot. Ok actually I "solved" this by upgrading to 128GB of RAM (before the rampocalypse), but still they should fix it.

[dead]

Re: Linux 7.2

#118

Earlier quoted context omitted.

I also have been using Linux for over 20 years and I agree that hardware support is the most noticable. This year I have installed Linux Mint on computers from people who wanted to jump from Windows to Linux. Every time I booted via USB, installed Linux and 10 minutes later everything was working. This would not have happened 10 years ago. Back then there would always be an issue with a video driver, WiFi driver or a…

> This would not have happened 10 years ago. Funny you say that, as I was installing Ubuntu on peoples laptops and it just worked, like 15 years ago... :-)

"I installed Ubuntu on peoples laptops and was extremely lucky they happened to have compatible hardware or didn't notice the stuff that didn't work and had a non-borked firmware". FTFY.

This was absolutely not everyones experience, including mine.

Re: Linux 7.2

#119
post #73

Earlier quoted context omitted.

Strongly disagree. Hardware support improved by leaps and bounds last decade and a half. Namespace isolation and cgroups driven containerization. eBPF appeared and gained adoption. Async I/O (and later just everything async) converged on io_uring. Btrfs is _stable_ - some people believed it would never be possible, ever. All kinds of scheduling were iterated and iterated over. All these things are visible across the…

btrfs is stable?? I used it a couple of years ago and really didn’t have a positive experience. I’ve found ZFS much more stable

It's basically fine as long as you read the release notes carefully and don't do anything the release notes say not to do (e.g. RAID5, let the disk fill up). It still has some sharp edges, but they're all documented.

Re: Linux 7.2

#120

It is funny with Linux (the kernel). From the outside it looks like almost nothing ever changes. You switch the computer on, it works away in the background to bring up the desktop and have everything talk. From that perspective it feels like nothing has changed in decades. But then you look at the change log, and almost everything you see added sounds really useful to someone working on this stuff. 35 years of work…

Isn't this the case with most well established software?

There is still a lot of work done on the background, perhaps even more than ever.

But unless you are a power user eagerly waiting for one of the things currently worked on, you wouldn't notice or care unless the interface changes (which usually only happens on visual interfaces).

Post reply on HN