From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dmitry Monakhov <dmonakhov@openvz.org>
Subject: [PATCH 0/4] ioengine: File based ioengines
Date: Wed, 19 Sep 2012 23:22:52 +0400
Message-ID: <1348082576-10528-1-git-send-email-dmonakhov@openvz.org>
Cc: axboe@kernel.dk, Dmitry Monakhov <dmonakhov@openvz.org>
To: linux-ext4@vger.kernel.org, fio@vger.kernel.org
Return-path: <linux-ext4-owner@vger.kernel.org>
Received: from mail-lb0-f174.google.com ([209.85.217.174]:54003 "EHLO
	mail-lb0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750720Ab2ISTXB (ORCPT
	<rfc822;linux-ext4@vger.kernel.org>); Wed, 19 Sep 2012 15:23:01 -0400
Sender: linux-ext4-owner@vger.kernel.org
List-ID: <linux-ext4.vger.kernel.org>

Fio is very cool tool for generating various io patterns.
And I use it as a base io-loader for xfsstress framework

I've prepared two file-based ioengines which allow to generate
interesting io patterns. 'falloc' is more generic and may be useful
for many cases, other 'e4defrag' is more specific but still
usfull. It would be nice to have this engines in-tree if possible.

TOC:
 # fixes for external engines
 export file_lookup_open
 ioengine: allow several external ioengines
 # file based ioengines
 ioengine: Add fallocate ioengine
 ioengine: Add e4defrag ioengine