From: Rik van Riel <riel@conectiva.com.br>
To: Philipp Rumpf <prumpf@mandrakesoft.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] documentation mm.h + swap.h
Date: Fri, 9 Mar 2001 19:39:59 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.33.0103091938430.2283-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <20010309021523.A13408@mandrakesoft.mandrakesoft.com>
On Fri, 9 Mar 2001, Philipp Rumpf wrote:
> On Thu, Mar 08, 2001 at 06:10:16PM -0300, Rik van Riel wrote:
> > --- linux-2.4.2-doc/include/linux/mm.h.orig Wed Mar 7 15:36:32 2001
> > +++ linux-2.4.2-doc/include/linux/mm.h Thu Mar 8 09:54:22 2001
> > @@ -39,32 +39,37 @@
> > * library, the executable area etc).
> > */
> > struct vm_area_struct {
> > - struct mm_struct * vm_mm; /* VM area parameters */
> > - unsigned long vm_start;
> > - unsigned long vm_end;
> > + struct mm_struct * vm_mm; /* The address space we belong to. */
> > + unsigned long vm_start; /* Our start address within vm_mm. */
> > + unsigned long vm_end; /* Our end address within vm_mm. */
>
> it might be a good idea to point out that this is the address of
> the byte after the last one covered by the vma, not the address
> of the last byte.
unsigned long vm_end; /* The first byte after our end address
within vm_mm. */
Does this look good to you ?
> (are there any architectures where we allow a vma at the end of
> memory ? Is the mm/ code handling ->vm_end = 0 correctly ?)
Good question ...
> > /*
> > + * Each physical page in the system has a struct page associated with
^^^^^^^^
> Each page of "real" RAM.
> > + *
> > + * TODO: make this structure smaller, it could be as small as 32 bytes.
>
> Or make it cover large pages, which might be even more of a win ..
*nod*
regards,
Rik
--
Linux MM bugzilla: http://linux-mm.org/bugzilla.shtml
Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...
http://www.surriel.com/
http://www.conectiva.com/ http://distro.conectiva.com/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-03-09 22:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-08 21:10 Rik van Riel
2001-03-09 8:15 ` Philipp Rumpf
2001-03-09 22:39 ` Rik van Riel [this message]
[not found] <Pine.LNX.4.33.0103081807260.1314-100000@duckman.distro.con ectiva>
2001-03-09 0:39 ` Anton Altaparmakov
2001-03-09 22:22 ` Rik van Riel
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=Pine.LNX.4.33.0103091938430.2283-100000@duckman.distro.conectiva \
--to=riel@conectiva.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=prumpf@mandrakesoft.com \
/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