I can leave it as it is and do it on main thread. The question is how much X is in '
every X number of I/O' to make it reasonable? Any suggestions here?
From: SPDK [mailto:email@example.com] On Behalf Of Lance Hartmann ORACLE
Sent: Tuesday, October 30, 2018 7:44 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] perf vs spdk_app_start()
On Oct 30, 2018, at 12:55 PM, Walker, Benjamin
On Tue, 2018-10-30 at 09:59 +0000, Szwed, Maciej wrote:
> This is actually the case. I need to register poller for event
> handler and that is way I would like to use spdk_app_start. Creating
> own thread for poller is a bit overkill for example application.
The primary reason NVMe perf does not use the application framework is
because NVMe perf was written before the application framework
existed. You could definitely do a port to use it, but I kind of like
the independence. Any API you create in the NVMe driver should be
consumable without the application framework. Maybe just poll for events every X number
I'd like to cast a vote for retaining nvme/perf as-is as well. I found it very useful
in learning the use of the SPDK nvme driver API without having to wade through the
additional complexity of the app framework.
SPDK mailing list