Subject: Re: [Patch 0/5] I/O statistics through request queues
From: martin <mp3@de.ibm.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
In-Reply-To: <20061025104217.GB4281@kernel.dk>
References: <1161435423.3054.111.camel@dyn-9-152-230-71.boeblingen.de.ibm.com>
	 <20061023113728.GM8251@kernel.dk> <453D05C3.7040104@de.ibm.com>
	 <20061023200220.GB4281@kernel.dk> <453E38FE.1020306@de.ibm.com>
	 <20061024162050.GK4281@kernel.dk> <453E9C18.70803@de.ibm.com>
	 <20061025051238.GO4281@kernel.dk> <453F3D4E.4020608@de.ibm.com>
	 <20061025104217.GB4281@kernel.dk>
Content-Type: text/plain
Date: Thu, 02 Nov 2006 15:39:16 +0100
Message-Id: <1162478356.6902.144.camel@dix>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 683
Lines: 16

Jens, Andrew,
I am not pursueing this patch set. I have convinced myself that blktrace
is capable of being used as a an analysis tool for low level I/O
performance, if invoced with appropriate settings. In our tests, we
limited traces to Issue/Complete events, cut down on relay buffers, and
redirected traces to a network connection instead of filling locally
attached storage up. Cost is about 2 percent, as advertised.

Thanks,
Martin

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/