From: William Lee Irwin III <wli@holomorphy.com>
To: Samuel Ortiz <sortiz@dbear.engr.sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Rik van Riel <riel@conectiva.com.br>,
linux-mm@kvack.org
Subject: Re: [PATCH] rmap 13a
Date: Wed, 8 May 2002 04:13:49 -0700 [thread overview]
Message-ID: <20020508111349.GI15756@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0205080346450.31184-100000@dbear.engr.sgi.com>
On Wed, May 08, 2002 at 04:06:58AM -0700, Samuel Ortiz wrote:
> Some discontiguous architectures (ARM, for example) may be interested in
> getting rid of page->virtual, and thus shrinking the struct page size.
> So you may want to get the possibility of having
> (!CONFIG_HIGHMEM)&&CONFIG_DISCONTIGMEM and not wanting page->virtual.
> So, WANT_PAGE_VIRTUAL can not be defined with CONFIG_HIGHMEM ||
> CONFIG_DISCONTIGMEM.
> However, I should modify my patch in order for the changes to take place
> only if (!CONFIG_HIGHMEM)&&(CONFIG_DISCONTIG_MEM)&&(!WANT_PAGE_VIRTUAL).
> I can come back with the right changes if that makes sense to you.
Also, to be perfectly clear despite my message of perhaps extreme
conservatism regarding space conservation, I believe the time/space
tradeoff is an architectural consideration. Though I specifically
requested that a calculated UNMAP_NR_DENSE() be implemented, I by no
means oppose the usage of page->virtual for those architectures where
demonstrable performance benefits arise from the additional space
consumption of the extra field.
Cheers,
Bill
--
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/
next prev parent reply other threads:[~2002-05-08 11:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 2:17 Rik van Riel
2002-05-07 17:37 ` Christoph Hellwig
2002-05-07 18:03 ` William Lee Irwin III
2002-05-08 11:06 ` Samuel Ortiz
2002-05-08 11:13 ` William Lee Irwin III [this message]
2002-05-08 13:40 ` Rik van Riel
2002-05-08 18:21 ` Roman Zippel
2002-05-08 21:34 ` William Lee Irwin III
2002-05-08 22:34 ` Roman Zippel
2002-05-08 22:42 ` William Lee Irwin III
2002-05-08 22:50 ` William Lee Irwin III
2002-05-08 23:26 ` Roman Zippel
2002-05-09 1:29 ` William Lee Irwin III
2002-05-09 12:33 ` Roman Zippel
2002-05-09 14:09 ` William Lee Irwin III
2002-05-09 15:36 ` Roman Zippel
2002-05-09 17:42 ` William Lee Irwin III
2002-05-09 21:45 ` Roman Zippel
2002-05-09 23:13 ` William Lee Irwin III
2002-05-10 11:37 ` Roman Zippel
2002-05-10 16:28 ` William Lee Irwin III
2002-05-10 19:48 ` Roman Zippel
2002-05-08 21:50 ` William Lee Irwin III
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=20020508111349.GI15756@holomorphy.com \
--to=wli@holomorphy.com \
--cc=hch@infradead.org \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=sortiz@dbear.engr.sgi.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