linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Subject: Re: [uml-devel] Review needed for ubd fixes
Date: Wed, 21 Sep 2005 21:06:38 +0200	[thread overview]
Message-ID: <200509212106.39169.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20050921180436.GA7712@ccure.user-mode-linux.org>

On Wednesday 21 September 2005 20:04, Jeff Dike wrote:
> On Wed, Sep 21, 2005 at 05:49:43PM +0200, Blaisorblade wrote:
[...]
> > Don't think it's reasonable to expect this. I think that filesystems like
> > ext2 will never produce write barriers - they are needed for journaled
> > FS's.

> I thought your point was to rely on the block layer to order overlapping
> writes for us.
The block layer is supposed to merge as far as possible overlapping writes, 
that's reasonable, but not dependable. Say it gets the overlapping request 
*after* it sent the first one - we'll see both. Also, this is trivially true 
for output done through page cache, but for the rest I don't know if explicit 
merging is implemented.

For the buffer cache (i.e. fs metadata) it may still hold, but I'm not sure at 
all. Not that it matters for us - we can't depend on it anyway.

No, I was thinking to you enforcing ordering to comply to what journaled 
filesystems expect.

Btw: even when we aren't using COW, we're supposed to do writes in the order 
the fs passed them to us - at least when write barriers are explicitly sent 
(don't know if there's something to care normally - I know this as a LWN.net 
reader, not as an hacker in this area).

> It sounded reasonable to me :-)

> 				Jeff

-- 
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade

	

	
		
___________________________________ 
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB 
http://mail.yahoo.it



-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2005-09-21 19:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-17 22:45 [uml-devel] Review needed for ubd fixes Jeff Dike
2005-09-20 12:01 ` Blaisorblade
2005-09-20 19:06   ` Jeff Dike
2005-09-21 15:49     ` Blaisorblade
2005-09-21 18:04       ` Jeff Dike
2005-09-21 19:06         ` Blaisorblade [this message]
2005-09-21 20:45           ` Jeff Dike
2005-09-22 20:51             ` Blaisorblade
2005-09-27 18:12               ` Jeff Dike
2005-09-28 12:14                 ` Blaisorblade
2005-09-28 15:54                   ` Jeff Dike
2005-09-28 16:47                     ` Blaisorblade

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=200509212106.39169.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=bstroesser@fujitsu-siemens.com \
    --cc=jdike@addtoit.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox