Shaya Potter

depends. a sata ssd is only going to get 300MB/s if its only doing that (nvme obviously can do much better, spinning will do much worse, especially under io load)....

speaking from experience, when my storage is starved for iops, performance goes into the crapper. i.e. even if normally I can manage 150-200MB/s on spinning disk, I'm lucky to get...

I wasn't asking to get rid of the current mechanism, just a new mechaism for uploading a single (large) file with obfuscation so that a password doesn't really matter. and...

SSDs only have a limited amount of writes they can take. (i.e. 1000TB of writes is a good SSD).

as an example https://www.ontrack.com/uk/blog/pieces-of-interest/how-long-do-ssds-really-last/ "On its website, Samsung even promises that the product is withstanding up to 600 terabytes written (TBW)."

it seems mx player knows how to play hardware accelerated vc-1. tested last night and it shows its regular hw icon. when one switches it to sw decoding, it becomes...

I guess what worries me about it not being in RM_Call is the ability to not sanity check it well. i.e. I was considering putting in a validator like this...

also forgot to increment the flag bit from previous one, but probably doesn't matter if we want the new API approach.

updated PR/Comment/Title per @oranagra's suggestion.

can an RM_DrainPropagationQueue() occur in all module contexts (where one might run an RM_Call) safely?