From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Elizabeth Figura <zfigura@codeweavers.com>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
wine-devel@winehq.org, "André Almeida" <andrealmeid@igalia.com>,
"Wolfram Sang" <wsa@kernel.org>,
"Arkadiusz Hiler" <ahiler@codeweavers.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Andy Lutomirski" <luto@kernel.org>,
linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org,
"Randy Dunlap" <rdunlap@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>, "Will Deacon" <will@kernel.org>,
"Waiman Long" <longman@redhat.com>,
"Boqun Feng" <boqun.feng@gmail.com>
Subject: Re: [PATCH v7 00/30] NT synchronization primitive driver
Date: Tue, 7 Jan 2025 18:06:03 +0100 [thread overview]
Message-ID: <2025010738-amicably-art-f746@gregkh> (raw)
In-Reply-To: <20241213193511.457338-1-zfigura@codeweavers.com>
On Fri, Dec 13, 2024 at 01:34:41PM -0600, Elizabeth Figura wrote:
> This patch series implements a new char misc driver, /dev/ntsync, which is used
> to implement Windows NT synchronization primitives.
>
> NT synchronization primitives are unique in that the wait functions both are
> vectored, operate on multiple types of object with different behaviour (mutex,
> semaphore, event), and affect the state of the objects they wait on. This model
> is not compatible with existing kernel synchronization objects or interfaces,
> and therefore the ntsync driver implements its own wait queues and locking.
>
> This patch series is rebased against the "char-misc-next" branch of
> gregkh/char-misc.git.
>
> == Background ==
>
> The Wine project emulates the Windows API in user space. One particular part of
> that API, namely the NT synchronization primitives, have historically been
> implemented via RPC to a dedicated "kernel" process. However, more recent
> applications use these APIs more strenuously, and the overhead of RPC has become
> a bottleneck.
>
> The NT synchronization APIs are too complex to implement on top of existing
> primitives without sacrificing correctness. Certain operations, such as
> NtPulseEvent() or the "wait-for-all" mode of NtWaitForMultipleObjects(), require
> direct control over the underlying wait queue, and implementing a wait queue
> sufficiently robust for Wine in user space is not possible. This proposed
> driver, therefore, implements the problematic interfaces directly in the Linux
> kernel.
>
> This driver was presented at Linux Plumbers Conference 2023. For those further
> interested in the history of synchronization in Wine and past attempts to solve
> this problem in user space, a recording of the presentation can be viewed here:
>
> https://www.youtube.com/watch?v=NjU4nyWyhU8
>
>
> == Performance ==
>
> The performance measurements described below are copied from earlier versions of
> the patch set. While some of the code has changed, I do not currently anticipate
> that it has changed drastically enough to affect those measurements.
>
> The gain in performance varies wildly depending on the application in question
> and the user's hardware. For some games NT synchronization is not a bottleneck
> and no change can be observed, but for others frame rate improvements of 50 to
> 150 percent are not atypical. The following table lists frame rate measurements
> from a variety of games on a variety of hardware, taken by users Dmitry
> Skvortsov, FuzzyQuils, OnMars, and myself:
>
> Game Upstream ntsync improvement
> ===========================================================================
> Anger Foot 69 99 43%
> Call of Juarez 99.8 224.1 125%
> Dirt 3 110.6 860.7 678%
> Forza Horizon 5 108 160 48%
> Lara Croft: Temple of Osiris 141 326 131%
> Metro 2033 164.4 199.2 21%
> Resident Evil 2 26 77 196%
> The Crew 26 51 96%
> Tiny Tina's Wonderlands 130 360 177%
> Total War Saga: Troy 109 146 34%
> ===========================================================================
>
>
> == Patches ==
>
> The intended semantics of the patches are broadly intended to match those of the
> corresponding Windows functions. For those not already familiar with the Windows
> functions (or their undocumented behaviour), patch 27/28 provides a detailed
> specification, and individual patches also include a brief description of the
> API they are implementing.
>
> The patches making use of this driver in Wine can be retrieved or browsed here:
>
> https://repo.or.cz/wine/zf.git/shortlog/refs/heads/ntsync7
>
Given a lack of complaints, I've now applied this to my testing tree.
Thanks for sticking with it!
greg k-h
next prev parent reply other threads:[~2025-01-07 17:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 19:34 [PATCH v7 00/30] NT synchronization primitive driver Elizabeth Figura
2024-12-13 19:34 ` [PATCH v7 01/30] ntsync: Return the fd from NTSYNC_IOC_CREATE_SEM Elizabeth Figura
2024-12-13 19:34 ` [PATCH v7 02/30] ntsync: Rename NTSYNC_IOC_SEM_POST to NTSYNC_IOC_SEM_RELEASE Elizabeth Figura
2024-12-13 19:34 ` [PATCH v7 03/30] ntsync: Introduce NTSYNC_IOC_WAIT_ANY Elizabeth Figura
2024-12-13 19:34 ` [PATCH v7 04/30] ntsync: Introduce NTSYNC_IOC_WAIT_ALL Elizabeth Figura
2024-12-13 19:34 ` [PATCH v7 05/30] ntsync: Introduce NTSYNC_IOC_CREATE_MUTEX Elizabeth Figura
2024-12-13 19:34 ` [PATCH v7 06/30] ntsync: Introduce NTSYNC_IOC_MUTEX_UNLOCK Elizabeth Figura
2024-12-13 19:34 ` [PATCH v7 07/30] ntsync: Introduce NTSYNC_IOC_MUTEX_KILL Elizabeth Figura
2024-12-13 19:34 ` [PATCH v7 08/30] ntsync: Introduce NTSYNC_IOC_CREATE_EVENT Elizabeth Figura
2024-12-13 19:34 ` [PATCH v7 09/30] ntsync: Introduce NTSYNC_IOC_EVENT_SET Elizabeth Figura
2024-12-13 19:34 ` [PATCH v7 10/30] ntsync: Introduce NTSYNC_IOC_EVENT_RESET Elizabeth Figura
2024-12-13 19:34 ` [PATCH v7 11/30] ntsync: Introduce NTSYNC_IOC_EVENT_PULSE Elizabeth Figura
2024-12-13 19:34 ` [PATCH v7 12/30] ntsync: Introduce NTSYNC_IOC_SEM_READ Elizabeth Figura
2024-12-13 19:34 ` [PATCH v7 13/30] ntsync: Introduce NTSYNC_IOC_MUTEX_READ Elizabeth Figura
2024-12-13 19:34 ` [PATCH v7 14/30] ntsync: Introduce NTSYNC_IOC_EVENT_READ Elizabeth Figura
2024-12-13 19:34 ` [PATCH v7 15/30] ntsync: Introduce alertable waits Elizabeth Figura
2024-12-13 19:34 ` [PATCH v7 16/30] selftests: ntsync: Add some tests for semaphore state Elizabeth Figura
2024-12-13 19:34 ` [PATCH v7 17/30] selftests: ntsync: Add some tests for mutex state Elizabeth Figura
2024-12-13 19:34 ` [PATCH v7 18/30] selftests: ntsync: Add some tests for NTSYNC_IOC_WAIT_ANY Elizabeth Figura
2024-12-13 19:35 ` [PATCH v7 19/30] selftests: ntsync: Add some tests for NTSYNC_IOC_WAIT_ALL Elizabeth Figura
2024-12-13 19:35 ` [PATCH v7 20/30] selftests: ntsync: Add some tests for wakeup signaling with WINESYNC_IOC_WAIT_ANY Elizabeth Figura
2024-12-13 19:35 ` [PATCH v7 21/30] selftests: ntsync: Add some tests for wakeup signaling with WINESYNC_IOC_WAIT_ALL Elizabeth Figura
2024-12-13 19:35 ` [PATCH v7 22/30] selftests: ntsync: Add some tests for manual-reset event state Elizabeth Figura
2024-12-13 19:35 ` [PATCH v7 23/30] selftests: ntsync: Add some tests for auto-reset " Elizabeth Figura
2024-12-13 19:35 ` [PATCH v7 24/30] selftests: ntsync: Add some tests for wakeup signaling with events Elizabeth Figura
2024-12-13 19:35 ` [PATCH v7 25/30] selftests: ntsync: Add tests for alertable waits Elizabeth Figura
2024-12-13 19:35 ` [PATCH v7 26/30] selftests: ntsync: Add some tests for wakeup signaling via alerts Elizabeth Figura
2024-12-13 19:35 ` [PATCH v7 27/30] selftests: ntsync: Add a stress test for contended waits Elizabeth Figura
2024-12-13 19:35 ` [PATCH v7 28/30] maintainers: Add an entry for ntsync Elizabeth Figura
2024-12-13 19:35 ` [PATCH v7 29/30] docs: ntsync: Add documentation for the ntsync uAPI Elizabeth Figura
2024-12-13 19:35 ` [PATCH v7 30/30] ntsync: No longer depend on BROKEN Elizabeth Figura
2025-01-07 17:06 ` Greg Kroah-Hartman [this message]
2025-01-07 19:42 ` [PATCH v7 00/30] NT synchronization primitive driver Peter Zijlstra
2025-01-07 21:10 ` Elizabeth Figura
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025010738-amicably-art-f746@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ahiler@codeweavers.com \
--cc=andrealmeid@igalia.com \
--cc=arnd@arndb.de \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=longman@redhat.com \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=shuah@kernel.org \
--cc=will@kernel.org \
--cc=wine-devel@winehq.org \
--cc=wsa@kernel.org \
--cc=zfigura@codeweavers.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).