All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: "Darrick J. Wong" <djwong@us.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] block: Add a trace point whenever a barrier IO request is  sent
Date: Wed, 21 Apr 2010 23:27:27 +0200	[thread overview]
Message-ID: <20100421212727.GY27497@kernel.dk> (raw)
In-Reply-To: <20100421205626.GA15607@tux1.beaverton.ibm.com>

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


  reply	other threads:[~2010-04-21 21:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21 20:56 [PATCH] block: Add a trace point whenever a barrier IO request is sent Darrick J. Wong
2010-04-21 21:27 ` Jens Axboe [this message]
2010-04-23 19:41   ` Darrick J. Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100421212727.GY27497@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=djwong@us.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.