Re: [x265] [PATCH] ThreadSafeInteger: change default lock into read write lock

How about this patch？ On Saturday, April 9, 2016, Ximing Cheng wrote: > With the two patches, I just do a simple test on my Windows PC, and I test > for several times and finally get the follow results: > > ./x265.exe --fps 30 --input-res 1280x720

Re: [x265] [PATCH] ThreadSafeInteger: change default lock into read write lock

Thank you for the patches. The Slim RW locks should be a performance improvement from the documentation. I'm not so sure about the POSIX RWlocks though. Did you do any performance testing - does the change in behaviour of the reconRow and framefilter locks improve performance? On Sun, Apr 3, 2016

[x265] [PATCH] ThreadSafeInteger: change default lock into read write lock

# HG changeset patch # User Ximing Cheng # Date 1459672199 -28800 # Sun Apr 03 16:29:59 2016 +0800 # Node ID 601877ef465c549efe24063afa0479a39e369010 # Parent 5b01678f6fb4e89e23cd41295592a9aa5d51d4ba ThreadSafeInteger: change default lock into read write lock diff

[x265] [PATCH] ThreadSafeInteger: change default lock into read write lock

# HG changeset patch # User Ximing Cheng # Date 1459670195 -28800 # Sun Apr 03 15:56:35 2016 +0800 # Node ID 4260ba22dac98d2b097fc6a03023e5ba578652fb # Parent 5b01678f6fb4e89e23cd41295592a9aa5d51d4ba ThreadSafeInteger: change default lock into read write lock diff