From: Jens Axboe <jens.axboe@oracle.com>
To: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
Cc: dm-devel@redhat.com, btrace <linux-btrace@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add UNPLUG traces to all appropriate places
Date: Thu, 8 Nov 2007 21:15:45 +0100 [thread overview]
Message-ID: <20071108201544.GB13741@kernel.dk> (raw)
In-Reply-To: <473319F3.30706@hp.com>
On Thu, Nov 08 2007, Alan D. Brunelle wrote:
> Added blk_unplug interface, allowing all invocations of unplugs to result
> in a generated blktrace UNPLUG. Previously, we saw a PLUG on each of the
> underlying devices, and an UNPLUG on the volume. This patch ensures that
> we see the UNPLUG calls for each of the underlying devices.
Looks fine Alan, applied.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <jens.axboe@oracle.com>
To: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
Cc: linux-kernel@vger.kernel.org, dm-devel@redhat.com,
btrace <linux-btrace@vger.kernel.org>
Subject: Re: [PATCH] Add UNPLUG traces to all appropriate places
Date: Thu, 08 Nov 2007 20:15:45 +0000 [thread overview]
Message-ID: <20071108201544.GB13741@kernel.dk> (raw)
In-Reply-To: <473319F3.30706@hp.com>
On Thu, Nov 08 2007, Alan D. Brunelle wrote:
> Added blk_unplug interface, allowing all invocations of unplugs to result
> in a generated blktrace UNPLUG. Previously, we saw a PLUG on each of the
> underlying devices, and an UNPLUG on the volume. This patch ensures that
> we see the UNPLUG calls for each of the underlying devices.
Looks fine Alan, applied.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <jens.axboe@oracle.com>
To: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
Cc: linux-kernel@vger.kernel.org, dm-devel@redhat.com,
btrace <linux-btrace@vger.kernel.org>
Subject: Re: [PATCH] Add UNPLUG traces to all appropriate places
Date: Thu, 8 Nov 2007 21:15:45 +0100 [thread overview]
Message-ID: <20071108201544.GB13741@kernel.dk> (raw)
In-Reply-To: <473319F3.30706@hp.com>
On Thu, Nov 08 2007, Alan D. Brunelle wrote:
> Added blk_unplug interface, allowing all invocations of unplugs to result
> in a generated blktrace UNPLUG. Previously, we saw a PLUG on each of the
> underlying devices, and an UNPLUG on the volume. This patch ensures that
> we see the UNPLUG calls for each of the underlying devices.
Looks fine Alan, applied.
--
Jens Axboe
next prev parent reply other threads:[~2007-11-08 20:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 14:15 [PATCH] Add UNPLUG traces to all appropriate places Alan D. Brunelle
2007-11-08 14:15 ` Alan D. Brunelle
2007-11-08 20:15 ` Jens Axboe [this message]
2007-11-08 20:15 ` Jens Axboe
2007-11-08 20:15 ` Jens Axboe
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=20071108201544.GB13741@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=Alan.Brunelle@hp.com \
--cc=dm-devel@redhat.com \
--cc=linux-btrace@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.