linux-um archives
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: "Montgomery, Kendal L" <kendal.montgomery@qwest.com>
Cc: user-mode-linux-devel@lists.sourceforge.net, jdike@sonycom.com
Subject: Re: [uml-devel] Separate COW patch.
Date: Mon, 06 Oct 2003 17:23:42 -0400	[thread overview]
Message-ID: <200310062123.h96LNhGj020809@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Mon, 29 Sep 2003 11:53:40 CDT." <2D4B6CD74137D4119A1100104BC6BCBF0BC58605@dubntex006.qwest.net>

kendal.montgomery@qwest.com said:
> Where can I get what you've worked on so far?  I'd be willing to give
> it a try and possibly help to sort out the remaining pieces that need
> to make it work. 

It's in arch/um/drivers/cow_kern.c.  The bit that got me hung up was ensuring
that COW bitmap updates happen before the actual I/O.  This is necessary
in case the UML crashes during a write.  You want the bitmap update to
happen only after the data has been written.

				Jeff



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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:[~2003-10-06 21:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-29 16:53 [uml-devel] Separate COW patch Montgomery, Kendal L
2003-10-06 21:23 ` Jeff Dike [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-26 22:45 Montgomery, Kendal L
2003-09-26 23:14 ` Goetz Bock
2003-09-27  0:02 ` Jeff Dike
2003-09-27 22:56 ` Michael Richardson
2003-09-28  0:00 ` Paul Sladen
2003-09-28  1:44 ` Matt Zimmerman

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=200310062123.h96LNhGj020809@ccure.karaya.com \
    --to=jdike@addtoit.com \
    --cc=jdike@sonycom.com \
    --cc=kendal.montgomery@qwest.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