Announcement

Collapse
No announcement yet.

OpenBSD Seeing Initial Work Land On Enabling 64-bit POWER

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • OpenBSD Seeing Initial Work Land On Enabling 64-bit POWER

    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?pag...ERPC64-Landing

  • #2
    Is it IBM Power or Freescale etc, PowerPC?
    Both?

    Comment


    • #3
      Originally posted by milkylainen View Post
      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

      Comment


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

        Comment


        • #5
          Originally posted by Mario Junior View Post
          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.

          Comment


          • #6
            Originally posted by aht0 View Post

            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.

            Comment


            • #7
              Originally posted by rene View Post
              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.
              Last edited by kpedersen; 05-18-2020, 03:17 PM.

              Comment


              • #8
                Originally posted by Mario Junior View Post
                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.

                Comment


                • #9
                  Originally posted by rene View Post
                  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

                  Comment


                  • #10
                    Originally posted by rene View Post

                    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.

                    Comment

                    Working...
                    X