From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
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 16:45:07 -0400 [thread overview]
Message-ID: <20050921204507.GA9918@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200509212106.39169.blaisorblade@yahoo.it>
On Wed, Sep 21, 2005 at 09:06:38PM +0200, Blaisorblade wrote:
> 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.
Yeah, I'm concerned about O_DIRECT. Also, what happens when we write a page
to disk, and immediately afterwards, it gets dirty again and written again?
Is there a barrier between the two?
> No, I was thinking to you enforcing ordering to comply to what journaled
> filesystems expect.
Yeah, but there's more ordering than that.
> 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).
We get requests from the block layer, not the fs. And physical disks are
allowed to reorder requests, so I think there is some flexibility there.
Jeff
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-09-21 21:28 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
2005-09-21 20:45 ` Jeff Dike [this message]
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=20050921204507.GA9918@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade@yahoo.it \
--cc=bstroesser@fujitsu-siemens.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