On 6/28/20 1:27 PM, Yigal Korman wrote: > When enabled, some of the more dependency-heavy internal engines are > converted to "plugin" engines, i.e. they are built into separate object > files and are loaded by fio on demand. > This helps downstream distros package these engines separately and not > force a long list of package dependencies from the base fio package. How does this impact the performance of the engine? It'd be interesting to run a test with something ala: fio --name=test --ioengine=null --size=100g --rw=randread --norandommap --gtod_reduce=1 with the current build, then apply these patches (and turn the null engine into an externally loadable engine, of course), and re-run the test case. For what it's worth, I like the change in general, as dependencies do pile on. But I'd like to ensure that we're not taking a performance hit for something like this. -- Jens Axboe
