Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756547Ab0DUV1a (ORCPT ); Wed, 21 Apr 2010 17:27:30 -0400 Received: from 0122700014.0.fullrate.dk ([95.166.99.235]:53281 "EHLO kernel.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755812Ab0DUV13 (ORCPT ); Wed, 21 Apr 2010 17:27:29 -0400 Date: Wed, 21 Apr 2010 23:27:27 +0200 From: Jens Axboe To: "Darrick J. Wong" Cc: linux-kernel , linux-ext4 Subject: Re: [PATCH] block: Add a trace point whenever a barrier IO request is sent Message-ID: <20100421212727.GY27497@kernel.dk> References: <20100421205626.GA15607@tux1.beaverton.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100421205626.GA15607@tux1.beaverton.ibm.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 592 Lines: 16 On Wed, Apr 21 2010, Darrick J. Wong wrote: > Simple debugging patch used to watch for barrier requests. I've been using > this to watch ext4's barrier=1 behavior. But barriers are already being logged, if you watch blkparse data, it'll be RB or WB events. So I don't see what this addition provides that we don't already have? -- Jens Axboe -- 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/