All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Doug Dumitru <doug@easyco.com>,
	"Vaibhav Sharma, Noida" <Vaibhavs@noida.hcltech.com>
Subject: Re: [uml-devel] memory
Date: Sun, 23 Jan 2005 04:51:19 -0500	[thread overview]
Message-ID: <200501230451.19196.rob@landley.net> (raw)
In-Reply-To: <41F36014.7050905@easyco.com>

On Sunday 23 January 2005 03:28 am, Doug Dumitru wrote:

> Mr. Sharma,
>
> What you are trying to do will work, but not for large amounts of
> memory.  UML runs the client using a single user mode memory block as
> the entire client's core.  Thus the clients core size is limited to what
> a single task can allocate as plain memory.  With x86 architechure cpus,
> this is 2G or 3G depending on how you build a kernel (but usually 2G).
> There are no paging mechanism here so there is no way to make it
> "gigabytes"
>
> Others can correct me if I have the exact numbers wrong.

UML uses mmap (generally of a /tmp file) as physical memory.  This can be way 
bigger than physical memory on the machine, sure, and the parent kernel will 
transparently use the mmaped file as backing store, demand paged and all 
that.  (Just like it would for any other application.)

You could run out of virtual address space, though.  Trying to map more than a 
few gigabytes on a 32 bit machine is unlikely to work.

Might I suggest buying a cheap x86-64 system (you can get 'em at Fry's a 
couple hundred bucks), feed it a cheap 300 gigabyte IDE drive, and have fun.

Rob


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
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-01-23 10:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-23  6:46 [uml-devel] memory Vaibhav  Sharma, Noida
2005-01-23  8:28 ` Doug Dumitru
2005-01-23  9:51   ` Rob Landley [this message]
2005-01-24 18:41     ` Blaisorblade
2005-01-23 18:27   ` Henrik Nordstrom
2005-01-23 18:25     ` Rob Landley
2005-01-24 10:02       ` Henrik Nordstrom
2005-01-24 18:52         ` Blaisorblade
2005-01-24  1:11 ` Jeff Dike
2005-01-24  5:10   ` Rob Landley
2005-01-24 10:12     ` Henrik Nordstrom
2005-01-24 11:31       ` Bodo Stroesser
2005-01-24 11:32         ` stian
     [not found]         ` <200501241811.j0OIBYXk002874@ccure.user-mode-linux.org>
2005-01-24 16:24           ` Bodo Stroesser
  -- strict thread matches above, loose matches on Subject: below --
2005-01-24  8:13 Vaibhav  Sharma, Noida
2005-01-24 12:43 ` Rob Landley
2005-01-24 19:07 ` Blaisorblade
2005-01-24 22:41   ` Henrik Nordstrom
2005-01-25  1:40     ` Rob Landley

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=200501230451.19196.rob@landley.net \
    --to=rob@landley.net \
    --cc=Vaibhavs@noida.hcltech.com \
    --cc=doug@easyco.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 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.