From patchwork Wed Sep 19 19:22:54 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [2/4] ioengine: allow several external ioengines From: Dmitri Monakho X-Patchwork-Id: 185195 Message-Id: <1348082576-10528-3-git-send-email-dmonakhov@openvz.org> To: linux-ext4@vger.kernel.org, fio@vger.kernel.org Cc: axboe@kernel.dk, Dmitry Monakhov Date: Wed, 19 Sep 2012 23:22:54 +0400 Currently only one external ioengine can be exported because it use hardcoded 'ioengine' symbol, but if we allow external modules to have ops symbol similar to it's name then several extrnal engines become possible. NOTE: Old linking layout preserved Signed-off-by: Dmitry Monakhov --- ioengines.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/ioengines.c b/ioengines.c index b43374e..c2a64cb 100644 --- a/ioengines.c +++ b/ioengines.c @@ -104,7 +104,9 @@ static struct ioengine_ops *dlopen_ioengine(struct thread_data *td, * Unlike the included modules, external engines should have a * non-static ioengine structure that we can reference. */ - ops = dlsym(dlhandle, "ioengine"); + ops = dlsym(dlhandle, engine_lib); + if (!ops) + ops = dlsym(dlhandle, "ioengine"); if (!ops) { td_vmsg(td, -1, dlerror(), "dlsym"); dlclose(dlhandle);