From: Linus Torvalds <torvalds@transmeta.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@zip.com.au>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] remap-file-pages-2.5.63-A0
Date: Mon, 3 Mar 2003 08:50:34 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.44.0303030849050.11244-100000@home.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0303031142190.24967-100000@localhost.localdomain>
On Mon, 3 Mar 2003, Ingo Molnar wrote:
>
> the attached patch, against BK-curr, is a preparation to make
> remap_file_pages() usable on swappable vmas as well. When 'swapping out'
> shared-named mappings the page offset is written into the pte.
>
> it takes one bit from the swap-type bits, otherwise it does not change the
> pte layout - so it should be easy to adapt any other architecture to this
> change as well. (this patch does not introduce the protection-bits-in-pte
> approach used in my previous patch.)
One question: Why?
What's wrong with just using the value we use now (0), and just
calculating the page from the vma/offset information? Why hide the offset
in the page tables, when there is no need for it?
Linus
--
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/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next prev parent reply other threads:[~2003-03-03 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 10:57 Ingo Molnar
2003-03-03 16:50 ` Linus Torvalds [this message]
2003-03-03 16:56 ` Ingo Molnar
2003-03-03 20:45 ` [patch] remap-file-pages-2.5.63-A1 Ingo Molnar
2003-03-03 11:00 [patch] remap-file-pages-2.5.63-A0 Somshekar. C. Kadam - CTD, Chennai.
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.44.0303030849050.11244-100000@home.transmeta.com \
--to=torvalds@transmeta.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
/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