linux-um archives
 help / color / mirror / Atom feed
From: Matthew Bloch <matthew@bytemark.co.uk>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH] Locking user-mode kernel RAM into host physical RAM
Date: Tue, 9 Dec 2003 00:14:18 +0000	[thread overview]
Message-ID: <200312090014.19246.matthew@bytemark.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0312090003010.14902-100000@filer.marasystems.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 08 December 2003 23:18, Henrik Nordstrom wrote:
> > That's my only argument as to why it should be included:  mlocked
> > kernels behave more predictably in a hosting environment!
>
> In principle I agree, but it is somewhat of a corner case. For most
> practical uses you should be able to get the same results with a correctly
> tuned VM on the host and having sufficient amount of memory to allow for a
> decent buffer/cache in addition to the UML memory usage. Only if you
> overbook the memory usage (including buffer/cache requirements on
> the host) should there be significant problems.

I'm guessing the people who are going to be most concerned with UML's 
performance are ISPs, who are trying to get the best performance from their 
expensive U of data centre rack space; maybe this is a niche case at the 
moment.  

I can believe that the kernel is making compromises in terms of buffer 
requirements after the 50-60% full mark (which is about when we've seen 
swapping as you predicted).  However after buying a certain amount of RAM for 
your box, it is *much* cheaper to compensate for the higher disc demands with 
arrays of fast discs than it is to put more RAM in.  This doesn't make the 
kernel perform well from that point of view, but it means customers get the 
performance and price they expect :)

cheers,

- -- 
Matthew Bloch                             Bytemark Hosting
                                  tel. +44 (0) 8707 455026
                        http://www.bytemark-hosting.co.uk/
          Dedicated Linux hosts from 15ukp ($26) per month
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/1RPaT2rVDg8aLXQRAnLSAJ0QUHDOKcKD5qfKfYpJBBGQOxzbVACeOgrh
wh5avXswOggsOpxuFblT8Is=
=1aJr
-----END PGP SIGNATURE-----



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&opÌk
_______________________________________________
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-12-09  0:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-08 16:39 [uml-devel] [PATCH] Locking user-mode kernel RAM into host physical RAM Matthew Bloch
2003-12-08 17:31 ` Matt Ayres
2003-12-08 18:02 ` Steven Pritchard
2003-12-08 18:57   ` [uml-devel] Re: chroot option Henrik Nordstrom
2003-12-08 22:04     ` Jeff Dike
2003-12-08 23:00       ` Henrik Nordstrom
2003-12-08 19:01 ` [uml-devel] [PATCH] Locking user-mode kernel RAM into host physical RAM Jeff Dike
2003-12-08 22:23   ` Matthew Bloch
2003-12-08 23:18     ` Henrik Nordstrom
2003-12-09  0:14       ` Matthew Bloch [this message]
2003-12-09 19:00   ` 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=200312090014.19246.matthew@bytemark.co.uk \
    --to=matthew@bytemark.co.uk \
    --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