From: Jens Axboe <jens.axboe@oracle.com>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCHSET block#for-2.6.29] block: simplify and fix empty barrier
Date: Fri, 12 Dec 2008 12:36:42 +0100 [thread overview]
Message-ID: <20081212113642.GN23742@kernel.dk> (raw)
In-Reply-To: <49421088.1050304@kernel.org>
On Fri, Dec 12 2008, Tejun Heo wrote:
> Jens Axboe wrote:
> > On Fri, Dec 12 2008, Tejun Heo wrote:
> >> Jens, did you have time to review this?
> >
> > Sorry yes, I thought I had sent a reply on this already, weird. I
> > committed it last week, and it's tested fine here.
>
> Ah... thanks. Next patchset brewing then. :-)
Excellent. Are you going forward with the explicit peek/dequeue
interface for elv_next_request()? If not, then I'll put some time into
that as I think it needs doing soon. But if you are, I'll happily do
something else instead.
--
Jens Axboe
next prev parent reply other threads:[~2008-12-12 11:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 4:32 [PATCHSET block#for-2.6.29] block: simplify and fix empty barrier Tejun Heo
2008-11-28 4:32 ` [PATCH 1/6] block: reorganize QUEUE_ORDERED_* constants Tejun Heo
2008-11-28 4:32 ` [PATCH 2/6] block: remove duplicate or unused barrier/discard error paths Tejun Heo
2008-11-28 4:32 ` [PATCH 3/6] block: make every barrier action optional Tejun Heo
2008-11-28 4:32 ` [PATCH 4/6] block: make barrier completion more robust Tejun Heo
2008-11-28 4:32 ` [PATCH 5/6] block: simplify empty barrier implementation Tejun Heo
2008-11-28 4:32 ` [PATCH 6/6] block: fix empty barrier on write-through w/ ordered tag Tejun Heo
2008-12-12 3:23 ` [PATCHSET block#for-2.6.29] block: simplify and fix empty barrier Tejun Heo
2008-12-12 6:34 ` Jens Axboe
2008-12-12 7:19 ` Tejun Heo
2008-12-12 11:36 ` Jens Axboe [this message]
2008-12-12 13:26 ` Tejun Heo
2008-12-12 13:28 ` 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=20081212113642.GN23742@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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.