All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Andi Kleen <andi@firstfloor.org>,
	dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Implement barrier support for single device DM devices
Date: Mon, 18 Feb 2008 10:31:23 +1100	[thread overview]
Message-ID: <20080217233123.GA155407@sgi.com> (raw)
In-Reply-To: <47B58EAA.8040405@msgid.tls.msk.ru>

On Fri, Feb 15, 2008 at 04:07:54PM +0300, Michael Tokarev wrote:
> Alasdair G Kergon wrote:
> > On Fri, Feb 15, 2008 at 01:08:21PM +0100, Andi Kleen wrote:
> >> Implement barrier support for single device DM devices
> >  
> > Thanks.  We've got some (more-invasive) dm patches in the works that
> > attempt to use flushing to emulate barriers where we can't just
> > pass them down like that.
> 
> I wonder if it's worth the effort to try to implement this.
> 
> As far as I understand (*), if a filesystem realizes that the
> underlying block device does not support barriers, it will
> switch to using regular flushes instead

No, typically the filesystems won't issue flushes, either.

> - isn't it the same
> thing as you're trying to do on an MD level?
> 
> Note that a filesystem must understand barriers/flushes on
> underlying block device, since many disk drives don't support
> barriers anyway.
> 
> (*) this is, in fact, an interesting question.  I still can't
> find complete information about this.  For example, how safe
> xfs is if barriers are not supported or turned off?  Is it
> "less safe" than with barriers?  Will it use regular cache
> flushes if barriers are not here?

Try reading at the XFS FAQ:

http://oss.sgi.com/projects/xfs/faq/#wcache

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  parent reply	other threads:[~2008-02-17 23:31 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-15 12:08 [PATCH] Implement barrier support for single device DM devices Andi Kleen
2008-02-15 12:20 ` Alasdair G Kergon
2008-02-15 13:07   ` Michael Tokarev
2008-02-15 14:20     ` Andi Kleen
2008-02-15 14:12       ` Alasdair G Kergon
2008-02-15 14:12         ` [dm-devel] " Alasdair G Kergon
2008-02-15 15:34         ` Andi Kleen
2008-02-15 15:34           ` [dm-devel] " Andi Kleen
2008-02-15 15:31           ` Alan Cox
2008-02-15 15:31             ` [dm-devel] " Alan Cox
2008-02-18 12:48         ` Ric Wheeler
2008-02-18 12:48           ` [dm-devel] " Ric Wheeler
2008-02-18 13:24           ` Michael Tokarev
2008-02-18 13:52             ` Ric Wheeler
2008-02-18 13:52               ` [dm-devel] " Ric Wheeler
2008-02-19  2:45               ` Alasdair G Kergon
2008-02-19  2:45                 ` [dm-devel] " Alasdair G Kergon
2008-05-16 19:55                 ` Mike Snitzer
2008-05-16 19:55                   ` [dm-devel] " Mike Snitzer
2008-05-16 21:48                   ` Andi Kleen
2008-05-16 21:48                     ` [dm-devel] " Andi Kleen
2008-02-18 22:16             ` David Chinner
2008-02-19  2:56               ` Alasdair G Kergon
2008-02-19  2:56                 ` [dm-devel] " Alasdair G Kergon
2008-02-19  5:36                 ` David Chinner
2008-02-19  5:36                   ` David Chinner
2008-02-19  9:43                 ` Andi Kleen
2008-02-19  9:43                   ` Andi Kleen
2008-02-19  7:19               ` Jeremy Higdon
2008-02-19  7:19                 ` [dm-devel] " Jeremy Higdon
2008-02-19  7:58                 ` Michael Tokarev
2008-02-20 13:38                 ` Ric Wheeler
2008-02-20 13:38                   ` [dm-devel] " Ric Wheeler
2008-02-21  3:29                 ` Neil Brown
2008-02-21  3:29                   ` [dm-devel] " Neil Brown
2008-02-21  3:39               ` Neil Brown
2008-02-17 23:31     ` David Chinner [this message]
2008-02-19  2:39     ` Alasdair G Kergon
2008-02-19  2:39       ` Alasdair G Kergon
2008-02-19 11:12       ` David Chinner

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=20080217233123.GA155407@sgi.com \
    --to=dgc@sgi.com \
    --cc=andi@firstfloor.org \
    --cc=dm-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    /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.