Linux 6.14-rc1 Released With NTSYNC Completed, AMDXDNA Driver & Other Enhancements

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • phoronix
    Administrator
    • Jan 2007
    • 67370

    Linux 6.14-rc1 Released With NTSYNC Completed, AMDXDNA Driver & Other Enhancements

    Phoronix: Linux 6.14-rc1 Released With NTSYNC Completed, AMDXDNA Driver & Other Enhancements

    Linus Torvalds just released Linux 6.14-rc1 to cap off the Linux 6.14 merge window...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite
  • erniv2
    Senior Member
    • Apr 2022
    • 282

    #2
    Wanted to be 1st .

    Ok serious question, with NTSYNC in the Kernel, will we see esync and fsync deprecated in the near Future i dont see why wine needs 3 API´s in the Kernel.

    Discuss .

    Comment

    • mobadboy
      Senior Member
      • Jul 2024
      • 176

      #3
      classic game devs too stupid to support the most popular operating system in the world given android and docker

      Comment

      • shmerl
        Senior Member
        • Dec 2009
        • 3512

        #4
        Very cool! Now it will be possible to easier build Wine with ntsync in the headers too.

        Comment

        • shmerl
          Senior Member
          • Dec 2009
          • 3512

          #5
          Originally posted by erniv2 View Post
          Wanted to be 1st .

          Ok serious question, with NTSYNC in the Kernel, will we see esync and fsync deprecated in the near Future i dont see why wine needs 3 API´s in the Kernel.

          Discuss .
          Yes, naturally. It's possible upstream wine will drop esync from staging once ntsync is merged and kernel is out. fsync isn't in upstream or staging, so it's up to Proton to decide what to do. I suspect Proton will be slower to use it, since it's focused on SteamOS kernel release schedule and it will probably be a while before it gets there.

          Comment

          • commiethebeastie
            Phoronix Member
            • Jun 2013
            • 53

            #6
            Originally posted by erniv2 View Post
            Wanted to be 1st .

            Ok serious question, with NTSYNC in the Kernel, will we see esync and fsync deprecated in the near Future i dont see why wine needs 3 API´s in the Kernel.

            Discuss .
            esync is not a specific kernel side feature, it's a simple posix open() caller.

            fsync could be useful for a native applications.

            Comment

            • oiaohm
              Senior Member
              • Mar 2017
              • 8469

              #7
              Originally posted by erniv2 View Post
              Wanted to be 1st .

              Ok serious question, with NTSYNC in the Kernel, will we see esync and fsync deprecated in the near Future i dont see why wine needs 3 API´s in the Kernel.

              Discuss .
              Wine esync is not esync in kernel its eventfd.

              Wine fsync is not fsync in kernel or api call but futex.


              These APIs were developed for other applications not wine. Wine tried to make them fit so they are going no where.

              eventfd and futex work great for other applications. They don't work for what wine project needs as copy windows behaviors.
              Last edited by oiaohm; 02 February 2025, 11:30 PM.

              Comment

              • oiaohm
                Senior Member
                • Mar 2017
                • 8469

                #8
                Originally posted by commiethebeastie View Post
                esync is not a specific kernel side feature, it's a simple posix open() caller.

                fsync could be useful for a native applications.
                No wrong. https://github.com/Kron4ek/wine-tkg/...r/README.esync esync is eventfd not based on simple posix open call. Yes the open function of eventfd is the command eventfd not the posix open..

                wine fsync is futex when you look it up.

                ntsync replaces the old prototype wine project fastsync work that was a DKMS loadable module.

                Comment

                • mirmirmir
                  Senior Member
                  • Jan 2021
                  • 584

                  #9
                  Originally posted by shmerl View Post

                  Yes, naturally. It's possible upstream wine will drop esync from staging once ntsync is merged and kernel is out. fsync isn't in upstream or staging, so it's up to Proton to decide what to do. I suspect Proton will be slower to use it, since it's focused on SteamOS kernel release schedule and it will probably be a while before it gets there.
                  What about macos? Do the not use esync?

                  Comment

                  • oiaohm
                    Senior Member
                    • Mar 2017
                    • 8469

                    #10
                    Originally posted by mirmirmir View Post
                    What about macos? Do the not use esync?
                    esync is eventfd based this has not been a feature of macos ever.

                    A Mach semaphore-based synchronization mechanism for Wine on macOS. Built for speed, inspired by fsync. - marzent/wine-msync

                    There is work to make something like esync using Mach primitives for Macos.

                    Comment

                    Working...
                    X