From: Matt Zimmerman <mdz@debian.org>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: more on COW (long)
Date: Mon, 19 Jan 2004 18:07:55 -0800 [thread overview]
Message-ID: <20040120020755.GF16181@alcor.net> (raw)
In-Reply-To: <20040119.155346.-522689.0.mcmechanjw@juno.com>
On Mon, Jan 19, 2004 at 03:53:43PM -0800, James W McMechan wrote:
> The setup in that case would be to use losetup to make devices using
> one for each COW and backing file so you can only have 1/2 of the
> available loops used for COW files and the other 1/2 as the backing
> files i.e. 4 COW files with 4 backing files from 8 loop back devices
> the usual default, as of Feb 2002 you can now have up to 256 loop
> devices. But I think that a hard limit of 128 COW files per system is
> too small, and if the max_loop is left at the default of 8... 4 COW files
> per system would be a great pain, (yes, if they all use the exact same
> backing file you could get 255 or 7)
Why do you need loop devices? Doing COW in the UML kernel can deal with ubd
block devices instead. This means chewing up two ubd devices for each COW
device, though, and I think is the opposite direction of where Jeff wants to
go.
--
- mdz
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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:[~2004-01-20 2:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 23:53 [uml-devel] Re: more on COW (long) James W McMechan
2004-01-20 2:07 ` Matt Zimmerman [this message]
2004-01-28 5:18 ` Jeff Dike
2004-01-28 5:55 ` Dan Shearer
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=20040120020755.GF16181@alcor.net \
--to=mdz@debian.org \
--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 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.