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

Alle 21:54, sabato 21 febbraio 2004, M A Young ha scritto:
> On Sat, 21 Feb 2004, BlaisorBlade wrote:
> > 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).
>
> That doesn't help you either, because increasing len within setup_physmem
> writes to memory that is going to be used for other purposes.
Why cannot we fix the other mmaps from the file?
> The only way
> around this amounts to increasing physmem_size anyway.

I must repeat myself: it seems that increasing physmem_size by, i.e., 4megas, 
when the user asked, i.e., for 32 mega, means that the kernel will have 
correctly 32mega of memory, but that it can try to access 36 mega of memory, 
right? I've actually checked that the statistics about how much memory it can 
use come from physmem_size, through init_maps() and mem_init():

        /* this will put all low memory onto the freelists */
        totalram_pages = free_all_bootmem();

Please, read this email and correct me on this point if I am wrong or confirm 
this behaviour.
-- 
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=1356&alloc_id=3438&op=click
_______________________________________________
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-22 15:38 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
2004-02-21 20:54       ` M A Young
2004-02-22 15:34         ` BlaisorBlade [this message]

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=200402221634.06668.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