Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Meta is using the Linux scheduler designed for Valve's Steam Deck on its servers

phoronix.com

Post reply on HN
Print view View original

251–260 of 407 posts

Re: Meta is using the Linux scheduler designed for Valve's Steam Deck on its servers

#251

Post by 0x1ch »

aucisson_masque wrote: post #224
Sparkyte wrote: post #171

I've been using Bazzite Desktop for 4 months now and it has been my everything. Windows is just abandonware now even with every update they push. It is clunky and hard to manage.

Isn't bazzite a gaming focused distribution ? It seems weird to install it on a PC that does 'my everything'. I wouldn't make excel spreadsheet on the steam deck for instance.

Bazzite is advertised for gamers, however from my understanding it's just Fedora Atomic wrapped up to work well on steamdeck adjacent hardware and gaming is a top priority. You'd still be receiving the same level of quality you would expect from Fedora/RHEL (I would think).

Re: Meta is using the Linux scheduler designed for Valve's Steam Deck on its servers

#252

Post by m4rtink »

theLiminator wrote: post #147
MarleTangible wrote: post #26

Earlier quoted context omitted.

Over time they're going to touch things that people were waiting for Microsoft to do for years. I don't have an example in mind at the moment, but it's a lot better to make the changes yourself than wait for OS or console manufacturer to take action.

Imagine if windows moved to the linux kernel and then used wine/proton to serve their own userspace.

It kinda looked like this is the future, about at the same time they introduced WSL, released dotNET for Linux and started contributing to the Linux Kernel - all the while making the bank with Azure mostly thanks to running Linux workloads.

But then they deCided it is better to show adds at OS level, rewrite OS UI as a web app, force harware DRM for their new OS version (TPM requirement) as well as automatically capturing content of you screen and feed it to AI.

Re: Meta is using the Linux scheduler designed for Valve's Steam Deck on its servers

#253

Post by m4rtink »

the_pwner224 wrote: post #170
baq wrote: post #99

Earlier quoted context omitted.

I low key hope the current DDR5 prices push them to drag the Linux memory and swap management into the 21st century, too, because hard locking on low memory got old a while ago

It takes a solid 45 seconds for me to enable zram (compressed RAM as swap) on a fresh Arch install. I know that doesn't solve the issue for 99% of people who don't even know what zram is / have no idea how to do it / are trying to do it for the first time, but it would be pretty easy for someone to enable that in a distro. I wouldn't be shocked if it is already enabled by default in Ubuntu or Fedora.

Zram has been enabled on Fedora by default since 2020:

https://fedoraproject.org/wiki/Changes/SwapOnZRAM

Re: Meta is using the Linux scheduler designed for Valve's Steam Deck on its servers

#254

Post by opello »

112233 wrote: post #175
onraglanroad wrote: post #138

Earlier quoted context omitted.

Since some of us could be bothered reading docs. Give it a try and see how it works out for you.

Some of us can! I certainly enjoy doing it, and according to "man 5 acl" what you assert is completely false. Unless you have a particular commit or document from kernel.org you had in mind?

> Each of these characters is replaced by the - character to denote that a permission is absent in the ACL entry.

Wouldn't the o::--- default ACL, like mode o-rwx, deny others access in the way you're describing?

Re: Meta is using the Linux scheduler designed for Valve's Steam Deck on its servers

#255

Post by cosmic_cheese »

johnny22 wrote: post #248
cosmic_cheese wrote: post #197

Earlier quoted context omitted.

One would've expected one of the many desktop-oriented distros (some with considerable funding, even) to have tackled these things already, but somehow desktop Linux has been stuck in the awkward midway of "it technically works, just learn to live with the rough edges" until finally Valve took initiative. Go figure.

Please don't erase all the groundwork they've done over the years to make it possible for these later enhancements to happen. It wasn't like they were twiddling their thumbs this whole time!

That's not my intention at all. It's just frustrating how little of it translates to impact that's readily felt by end users, including those of us without technical inclination.

Re: Meta is using the Linux scheduler designed for Valve's Steam Deck on its servers

#256

Post by m4rtink »

TulliusCicero wrote: post #76
tayo42 wrote: post #43

Earlier quoted context omitted.

I feel like I rarely see contacting out work go well. This seems like an exception

Valve contracts out to actually competent people and companies rather than giant bodycount consulting firms.

Not to mention the code being open source & in need to be accepted upstream to be actually useful in the long term.

Re: Meta is using the Linux scheduler designed for Valve's Steam Deck on its servers

#257

Post by carlwgeorge »

tremon wrote: post #156
dfedbeef wrote: post #67

Earlier quoted context omitted.

RHEL specifically makes it really annoying to see the source. You get a web view.

This violates the GPL, which explicitly states that recipients are entitled to the source tree in a form suitable for modification -- which a web view is not.

The source trees in a form suitable for modification (and pull requests) are here:

https://gitlab.com/redhat/centos-stream/rpms

Re: Meta is using the Linux scheduler designed for Valve's Steam Deck on its servers

#258

Post by crtasm »

trinsic2 wrote: post #88
crtasm wrote: post #68

Earlier quoted context omitted.

Their games and systems tie into huge gambling operations on 3rd party sites If you have 30mins for a video I recommend People Make Games' documentary on it https://www.youtube.com/watch?v=eMmNy11Mn7g

Yeah, im sorry. Valve is the last company people should be focusing for this type of behavior. All the other AAA game companies use these mechanics to deliberate manipulate players. IMHO valve doesn't use predatory practices to keep this stuff going.

How much of the video did you watch? I'm not aware of other game companies that enable 3rd party integrations into their item systems. This isn't just "lootboxes bad" - it's Valve profiting from actual gambling happening on external sites.

Re: Meta is using the Linux scheduler designed for Valve's Steam Deck on its servers

#259

Post by lawlessone »

ethbr1 wrote: post #199
dangus wrote: post #182

Earlier quoted context omitted.

Is that something Linux needs? I don’t really understand the benefit of it.

The more powerful form is the UAC full privilege escalation dance that Win 7+(?) does, which is a surprisingly elegant UX solution. 1. Snapshot the desktop 2. Switch to a separate secure UI session 3. Display the snapshot in the background, greyed out, with the UAC prompt running in the current session and topmost It avoids any chance of a user-space program faking or interacting with a UAC window. Clever way of deal…

>Display the snapshot in the background, greyed out,

Is there an offset. I could have sworn things always seemed offset to the side a little.

Re: Meta is using the Linux scheduler designed for Valve's Steam Deck on its servers

#260

Post by senderista »

dijit wrote: post #238
senderista wrote: post #228

Earlier quoted context omitted.

If that were true then presumably Microsoft wouldn't have ported it to Windows: https://learn.microsoft.com/en-us/windows/win32/api/ioringap... Although Windows registered network I/O (RIO) came before io_uring and for all I know might have been an inspiration: https://learn.microsoft.com/en-us/previous-versions/windows/...

That argument holds no water. IOUring is essential for the performance of some modern POSIX programs. You can see shims for fork() to stop tanking performance so hard too. IOUring doesnt map at all onto IOCP, at least the windows subtitute for fork has “ZwCreateProcess“ to work from. IOUring had nothing. IOCP is much nicer from a dev point of view because your program can be signalled when a buffer has data on it but…

The CQE for e.g. a successful read(2) operation will have the number of bytes read in the `res` field.
Post reply on HN