Prev: [PATCH v2.6.34-rc5 06/12] KEYS: Fix an RCU warning
Next: [PATCH v2.6.34-rc5 10/12] sched: Fix an RCU warning in print_task()
From: Darrick J. Wong on 23 Apr 2010 15:50
On Wed, Apr 21, 2010 at 11:27:27PM +0200, Jens Axboe wrote:
> 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?
I also have the function graph tracer turned on, so I can (try to) map barrier
requests to specific chunks of ext4 code. But, maybe there's a way to do this
with blkparse that I haven't found yet?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/