On Mon, Apr 10, 2017 at 8:45 PM, Deyoung Hong (dhong) <dhong@xxxxxxxxxx> wrote:
> Hi Jens,
>
> I have a couple basic questions:
>
> 1) If I want to submit a new IO engine with fio and it has a dependency on an external library, how does that work when fio is compiled? Please also point me to info how to submit a new IO engine to be packaged with fio?
>
> 2) I've seen cases where the ->iomem_alloc() function (i.e. for a custom IO engine) is invoked first by fio before ->get_file_size() or ->setup(). This causes an issue since IO memory allocation can have dependency on certain initialization (for the custom IO engine) that is done in ->get_file_size(). I just wonder if that's an fio bug or how it should be?
It sounds more like a misconception re iomem_{alloc,free} API. It is
about buffers I/O goes to/from, not files. As an example (and the root
cause behind the API proposal), I wanted to be able to allocate
buffers in DMAable memory as my engine required that to interact with
hardware directly.
Being unrelated to files by design, buffer initialization occurs way
before file setup as it did in fio before iomem_* API was introduced.
Regards,
Andrey
> My current work around is to check in ->iomem_alloc() each time and do initializion first if has not.
>
> Thanks,
> Deyoung
>
> --
> To unsubscribe from this list: send the line "unsubscribe fio" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe fio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
