All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: riel@conectiva.com.br, linux-mm@kvack.org,
	linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: rmap for ARMV.
Date: Tue, 19 Feb 2002 16:42:11 +0000	[thread overview]
Message-ID: <7261.1014136931@redhat.com> (raw)
In-Reply-To: <20020219161412.B16613@flint.arm.linux.org.uk>

linux@arm.linux.org.uk said:
>  When rmap gets merged into the 2.5 kernel series, I'll look at what
> can be done to sort out the pte situation - we could re-jig the page
> tables so a 'pgd' is 8 bytes per entry (made up of two hardware PTE
> pointers), the second level page tables end up being 2K hardware + 2K
> for Linux, which nicely maps to a page per PTE as viewed by Linux.

That would probably make sense - I didn't really want to do something that 
intrusive myself. In the meantime, this is also required:

--- linux-2.4.17-arm-rmap.patch	19 Feb 2002 15:59:41 -0000	1.1
+++ linux-2.4.17-arm-rmap.patch	19 Feb 2002 16:24:11 -0000
@@ -39,7 +39,7 @@
  	if (block & 2047)
  		BUG();
  
-@@ -475,11 +495,31 @@
+@@ -475,11 +495,32 @@
  			PTRS_PER_PTE * sizeof(pte_t), 0);
  }
  
@@ -54,6 +54,7 @@
 +		struct page * page = virt_to_page(pte);
 +
 +		kmem_cache_free(pte_rmap_cache, page->mapping);
++		page->mapping = NULL;
 +	}
 +}
 +


--
dwmw2


--
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-mm.org/

      reply	other threads:[~2002-02-19 16:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-19 16:01 rmap for ARMV David Woodhouse
2002-02-19 16:14 ` Russell King - ARM Linux
2002-02-19 16:42   ` David Woodhouse [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=7261.1014136931@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-mm@kvack.org \
    --cc=linux@arm.linux.org.uk \
    --cc=riel@conectiva.com.br \
    /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.