OPENBSD IS FINISHED AND BANKRUPT

phoronix.com/scan.php?page=news_item&px=OpenBSD-Disabling-SMT

>even worse support for SMP environments
LOL

Attached: 1280px-OpenBSD_Logo_-_Cartoon_Puffy_with_textual_logo_below.svg.png (1280x833, 192K)

Other urls found in this thread:

openbsd.org/lyrics.html
twitter.com/SFWRedditImages

>Our focus is security
>Intel's SMT/Hyperthreading has been shown repeatedly to be insecure
>Rather than try and work around it, we're going to just say fuck it and disable it all

I don't see the problem.

>running OpenBSD on Intel or AMD platforms
Are you fucking retarded? Linux has the best support for those platforms out of any open source operating systems. OpenBSD is only good for really old PCs or for embedded devices, and possibly servers (Linux is just as good for servers). Then NetBSD is for all the rest of the obscure shit that has no other software except the OEM loaded stuff.

yes, thank you for delivering very false info.

hope you keep shilling so this secure os stays under the millenial's radar.

op is a millenial shill and everything millenials touch become literal shit.

stay away from my ware

Fuck you OP

Indeed.

OpenBSD is a meme
>Filesystem
default FS doesn't even support SSD TRIM, and OpenBSD doesn't support anything modern like ZFS or BTRFS.
In the CIA triad of Confidentiality, Integrity, and Availability, availability seems to be the one that's lacking. Who cares how hack-resistant your system is if the data you're protecting is corrupted?
That's not even getting into the volume management stuff that's missing, and the snapshots, and the everything.
"b-b-but MUH BACKUPS!!"
You do realize that if the filesystem is not secure and does not protect against bitrot and corruption, your precious backups are going to be fucked, because you'll be backing up corrupted data. Who even knows how far you'll have to roll back in order to get to a clean state?
>Security
"Only two remote holes in the default install!!!!!!!"
Yay!
I hope you realize that this literally only applies to a base system install with absolutely no packages added. In other words, not exactly representative or meaningful towards... anything really
>Sustainability
A few years ago, OpenBSD was actually in danger of shutting down because they couldn't keep the fucking lights on. How could anyone see this as a system they could rely on, when it could be in danger of ending at any time?
>Standards-compliance
"B-But OpenBSD is written in strictly standards-compliant C! Clearly that's better than muh GNU virus!"
So you're not allowed to create extensions to the standard? You should only implement the standard and nothing more? Keep in mind that this is nothing like EEE, as the GNU extensions are Free Software, with freely available source code, as opposed to proprietary shite. People should be allowed to innovate and improve things.
If you're gonna be anal about standards-compliance, then why let people make their own implementations anyway? Why not have the standards organizations make one C implementation and force everyone to use it?

Attached: NOpenBSD.png (1000x1000, 168K)

>devs aren't skilled enough to work around in their outdated scheduler

LOL

Modern OpenBSD doesn't work on a K6-2.

Attached: IMG_20180224_054027.jpg (351x480, 27K)

if they disable SMT their OS will be just as bad as ReactOS

SMT is a weird hack anyway.
It gives a 30% speedup only in the very best scenario, but in practice it can actually slow things down.

the freebsd fags are seething

this is an openbsd thread you retard

based

Even the linked article said if you have more than two cores, it almost always reduces performance

nah i mean after all those freebsd fiascos they're doing everything they can to discredit openbsd

There it is. Always posting this one. Have a (you)

Attached: 1528632847863.jpg (2518x1024, 392K)

Guess I won't be using Atom N270s anymore

The linked article seems to confuse SMP and SMT

>No ZFS
>No Jails
It's been finished and bankrupt fool.

Improve your English, ranjeet

I'm going to stop using OpenBSD now.
I suggest you fellows do the same.

Attached: 1529108961833.jpg (800x759, 89K)

from what century did you come from?

wut?

freetards on full damage control

Theo protects us, don't worry.

no

freebsd samefag retards out in force today.

>Those wishing to toggle the OpenBSD SMT support can use the new hw.smt sysctl setting on OpenBSD/AMD64 and is being extended to cover CPUs from other vendors and architectures.

>tfw 7 more side channel exploits about to come out for intel

Linux is NEVER the answer.

Attached: LIBERATORS.jpg (906x1330, 370K)

>can be disabled
wtf Theo why u do dis

how isn't the only way to secure intel cpu to rip it out of motherboard?

OpenBSD is for safe, no speed

oh here we go. /v/ tier arguments

"muh hypterthreading"
"muh MAC"

from people who's technical thinking operates within marketing buzzword terminology.

>I'm going to stop using OpenBSD now.
ok

>I suggest you fellows do the same.
nah

so, netbsd then?

Is the no SSD Trim thing true and does it really matter that much

Attached: 15269189870980.jpg (811x1209, 68K)

>millennial
Why self claimed good posters are always above the age 30? Did you spend your miserable life mastering the art of posting on Jow Forums?

>tfw the one freebsd cuck who replies to this thread is offline
yea i'd say it matters. it'll shorten the life of your disk, but by how much i don't know.

tfw no nvidia support

There's none. Intel always has been garbage, OpenBSD always pointed out that Intel is garbage and their hardware is badly designed with insane flaws.

OpenBSD is the only true defender of freedom and security in the time of information technology, no other project is even remotely that close in regards of security, stability and well design ecosystem.

On top their documentation is excellent

Every time I distrohop, I always end up going back to that one broken piece of trash distro which rules them all .... WINDOWS

SMT (Hyper-Threading) makes things up to 25% or 30% faster *for applications written to exploit hyper-threading*.
For the typical ways in which OpenBSD is used (network server, etc.) it probably doesn't matter too much.
I suspect numerical applications would suffer, but OpenBSD is not exactly a platform for numerical work in the first place.

If you run a firewall or a web server the impact if probably negligible to null.

In fact they are pretty much saying that their scheduler is not really SMT-aware in the first place, so it probably has little effect.

NO, Intel is finished. That's another showcase, how flawed Intel CPU's are.

I have this same problem desu
The only thing I want windows for is photoshop because I do not know how to pirate it on other platforms

>2 releases per year
Don't forget that they come with original soundtracks.
openbsd.org/lyrics.html

Attached: 0nirbgzgqqz01.webm (489x223, 435K)

You'd have to be a real gullible sap to stick with Intel, a real fucking sucker.

Attached: Ovens-in-the-Auschwitz-crematorium.jpg (600x450, 92K)

>cia cat

Attached: Puffyanim.gif (100x100, 141K)

can someone explain to me the performance benefit of multithreading?

why would x264 perform better on 1c/2t than 1c/1t

If they divide the file into 2 pieces each thread can work on half. I at least think this is a simplification of how things work.

why would this have better performance though if it's just two pathways to the same resources

>freeBSD
wew
>so, netbsd then?
yes, or GNU/Linux.
It's true, and pic related is why it matters.

Attached: trim.png (589x626, 137K)

then use -current you spud

> Then NetBSD is for all the rest of the obscure shit that has no other software except the OEM loaded stuff.
This meme needs to end, NetBSD has fewer supported platforms than Linux, it hasn't been ported to a new ISA since 2007. Besides, 90% of obscure shit is already running linux.

Wish I could run openbsd on my laptop. My next laptop will definitely be one that runs well with openbsd

Hyper Threading is a meme as always and was a mistake

Attached: bresscott-:DD.png (801x1500, 973K)

The idea is to have as many threads as execution units.
But if you have a single execution unit, there is no particular reason to have two threads (unless you design your program to do some computation while the other thread is blocked in a system call). It's likely to make things slower.

Generally you want 8 threads for 8 execution units. With hyper-threading, 4 cores mean you have 8 execution units.

Hyper-Threading is a way to "fake" having more cores by allowing two threads to share many systems like caches, etc. It's a cheap way to increase the number of execution units without having too many additional gates. But that's precisely the security issue; if they share caches, etc. in a way that's a bit "promiscuous", one thread can spy on another (keeping in mind that the threads might be for different users, or even different VMs).

OpenBSD is disabling Hyper-threading, not multi-threading.

/tpg/

Any thoughts on Qubes?

SMT is like adding a second lane to a road. Sometimes one lane is sufficient but frequently with CPUs the one lane gets backed up by a process that is taking its sweet ass time and that process will be hogging all of the resources of the core while its doing "nothing". SMT allows other tasks to pass that process and make use of the resources that aren't being utilized at that moment. If there aren't a lot of process with frequent breaks SMT can cause a backup in its own way because there's still not extra parts to handle all of the tasks simultaneously so the processor may cause one active process to wait on another active process.

>It gives a 30% speedup only in the very best scenario
>Even the linked article said if you have more than two cores, it almost always reduces performance

There are few cases where SMT doesn't improve performance. 30% is like the average level of improvement in general not just in the best case. It's true that SMT doesn't always help but it helps so often that if you don't have a specific application that would benefit from disabling it you should leave it enabled. Or at least that's how it was. SMT is a very significant feature on modern chips. If Intel's implementation is really broken by design then that's going to be a huge problem, in particular with the server and enterprise segments which aren't going to appreciate the higher power usage and worse performance.

HAHAHAHAHAHAHA

Attached: intel pls.png (652x725, 126K)

>SMT doesn't improve performance

Hyperthreading =/= how other SMT works. You basically never get negative scaling (and the positive scaling can be much higher) on ryzen and on IBM's recent POWER chips. Intel just has a teeny tiny core that ends up with shitloads of resource contention.