OpenBSD Seeing Initial Work Land On Enabling 64-bit POWER

[phoronix]

Phoronix: OpenBSD Seeing Initial Work Land On Enabling 64-bit POWER

It's arguably long overdue but OpenBSD is seeing initial work on POWERPC64 enablement landing in its source tree...

http://www.phoronix.com/scan.php?page=news_item&px=OpenBSD-POWERPC64-Landing

[milkylainen]

Is it IBM Power or Freescale etc, PowerPC?
Both?

[aht0]

Is it IBM Power or Freescale etc, PowerPC?
Both?

From that Twitter link

MPC7500
@mpc7500v2
·
21h
No. New #PowerPC machines like #POWER9 from https://raptorcs.com

[Mario Junior]

The performance of OpenBSD on x86 is already complete shit, imagine what it will be in ppc64le...

[aht0]

The performance of OpenBSD on x86 is already complete shit, imagine what it will be in ppc64le...

Somehow I suspect OBSD users won't give flying fuck about "performance equaling complete shit" since their priorities lie elsewhere.

You can have extreme performance or extreme security. Can't have both. Just look at Intel CPU's for confirmation.

[rene]

Somehow I suspect OBSD users won't give flying fuck about "performance equaling complete shit" since their priorities lie elsewhere.

You can have extreme performance or extreme security. Can't have both. Just look at Intel CPU's for confirmation.

OpenBSD is not even extreme security, it is the same good old one address space, written in C, where one typo will buffer over, under run, use after free, null dereference etc. For extreme security you want a more modern, address space separated, multi server micro kernel ;-) preferably with a little C as possible.

[kpedersen]

null dereference

... isn't the worst thing in the world. Sure, it will crash but this page has been mprotect'ed to terminate upon access.

As for performance... It depends on if the OpenBSD guys have to disable many processor features in order to achieve some semblance of safety to protect their users.

[brad0]

The performance of OpenBSD on x86 is already complete shit, imagine what it will be in ppc64le...

Get back to me when Linux isn't complete and utter garbage.

[JustinTurdeau]

it is the same good old one address space, written in C, where one typo will buffer over, under run, use after free, null dereference etc. For extreme security you want a more modern, address space separated, multi server micro kernel ;-) preferably with a little C as possible.

t. Troll

[aht0]

OpenBSD is not even extreme security, it is the same good old one address space, written in C, where one typo will buffer over, under run, use after free, null dereference etc. For extreme security you want a more modern, address space separated, multi server micro kernel ;-) preferably with a little C as possible.

"If wishers were horses, beggars would ride".

Use of C is inevitable due OS's own origins. Within constraints set by circumstances they are doing their best to be as secure as possible.