All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Chris Mason <chris.mason@oracle.com>, Jan Kara <jack@suse.cz>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/2] Improvements for barrier-test scheduler
Date: Wed, 11 Jan 2012 20:26:45 +0100	[thread overview]
Message-ID: <4F0DE275.9090200@kernel.dk> (raw)
In-Reply-To: <20120111012227.GB2179@shiny>

On 01/11/2012 02:22 AM, Chris Mason wrote:
> Jens, is this something you want in 3.3, or would you like to let it
> cook for another release cycle?

Since it's a test/debug aid and it's already proven itself useful, I
don't see any reason to push it out another cycle.

-- 
Jens Axboe


      reply	other threads:[~2012-01-11 19:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11  0:44 [PATCH 0/2] Improvements for barrier-test scheduler Jan Kara
2012-01-11  0:44 ` [PATCH 1/2] barrier-test: Do not flush delayed queue for reads Jan Kara
2012-01-11  0:44 ` [PATCH 2/2] barrier-test: Allow filesystem to specify special test request Jan Kara
2012-01-11  1:22 ` [PATCH 0/2] Improvements for barrier-test scheduler Chris Mason
2012-01-11 19:26   ` Jens Axboe [this message]

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=4F0DE275.9090200@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=chris.mason@oracle.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@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.