linux-um archives
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: M A Young <m.a.young@durham.ac.uk>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: 2.4.24-1um - exec-shield - [PATCH][RFC] memory shortness fix
Date: Sat, 21 Feb 2004 16:51:27 +0100	[thread overview]
Message-ID: <200402211651.27584.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <Pine.LNX.4.58.0402202219290.23596@vega.dur.ac.uk>

Alle 23:23, venerdì 20 febbraio 2004, M A Young ha scritto:
> On Fri, 20 Feb 2004, BlaisorBlade wrote:
> > The simple fix would be IMHO to add in setup_physmem:
> >
> >   offset -= UML_ROUND_UP(brk_start) - UML_ROUND_UP(&_end);
>
> You can't do that because the memory you add to the physmem area isn't
> empty, but includes memory used for other purposes, and using memory twice
> isn't good!

Yes, you are perfectly right and what I wrote is at all foolish and stupid - I 
should have written len += UML_ROUND_UP(brk_start) - UML_ROUND_UP(&_end); (or 
something similar).

My idea was not about increasing the allocated memory by mmaping at an earlier 
offset, but about just increasing the length.

Just like increasing physmem_size but without changing how much memory thinks 
to have: IMHO, even with 256 Mega UML can crash, if it thinks to have 260 
mega, but it won't crash if it has 32 Mega and knows it has so little (it 
will swap or OOM, not crash). Right?

-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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:[~2004-02-21 15:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-16 20:04 [uml-devel] uml-patch-2.4.24-1 Jeff Dike
2004-02-20 17:37 ` [uml-devel] Re: 2.4.24-1um - exec-shield - [PATCH][RFC] memory shortness fix BlaisorBlade
2004-02-20 22:23   ` M A Young
2004-02-21 15:51     ` BlaisorBlade [this message]
2004-02-21 20:54       ` M A Young
2004-02-22 15:34         ` 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=200402211651.27584.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --cc=m.a.young@durham.ac.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