All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] brd: support barriers
Date: Wed, 15 Apr 2009 11:08:10 +0200	[thread overview]
Message-ID: <20090415090810.GU5178@kernel.dk> (raw)
In-Reply-To: <20090415082707.GA7685@wotan.suse.de>

On Wed, Apr 15 2009, Nick Piggin wrote:
> Hi Jens,
> Do you have a tree I can send this though? Is this the right way to
> do what I want?

It'll let the barriers through, so I think it does what you want :-)
I can put it in the block tree.

> 
> --
> 
> brd is always ordered (not that it matters, as it is defined not to
> survive when the system goes down). So tell the block layer it is
> ordered, which might be of help with testing filesystems.
> 
> Signed-off-by: Nick Piggin <npiggin@suse.de>
> ---
>  drivers/block/brd.c |    1 +
>  1 file changed, 1 insertion(+)
> 
> Index: linux-2.6/drivers/block/brd.c
> ===================================================================
> --- linux-2.6.orig/drivers/block/brd.c
> +++ linux-2.6/drivers/block/brd.c
> @@ -436,6 +436,7 @@ static struct brd_device *brd_alloc(int
>  	if (!brd->brd_queue)
>  		goto out_free_dev;
>  	blk_queue_make_request(brd->brd_queue, brd_make_request);
> +	blk_queue_ordered(brd->brd_queue, QUEUE_ORDERED_TAG, NULL);
>  	blk_queue_max_sectors(brd->brd_queue, 1024);
>  	blk_queue_bounce_limit(brd->brd_queue, BLK_BOUNCE_ANY);
>  

-- 
Jens Axboe


      reply	other threads:[~2009-04-15  9:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15  8:27 [patch] brd: support barriers Nick Piggin
2009-04-15  9:08 ` 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=20090415090810.GU5178@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    /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.