From: Dave Hansen <haveblue@us.ibm.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Magnus Damm <magnus@valinux.co.jp>,
linux-mm@kvack.org, Magnus Damm <damm@opensource.se>,
Andy Whitcroft <apw@shadowen.org>
Subject: Re: [RFC] Removing page->flags
Date: Thu, 09 Feb 2006 09:27:55 -0800 [thread overview]
Message-ID: <1139506075.9209.9.camel@localhost.localdomain> (raw)
In-Reply-To: <aec7e5c30602081850n772005bckf729683f446fb2a9@mail.gmail.com>
On Thu, 2006-02-09 at 11:50 +0900, Magnus Damm wrote:
> I realize that if struct page size is not a power of two we will end
> up with struct page elements that cross a lot of page boundaries. But
> is that really a problem? I thought we were safe if:
>
> 1) struct page could be any size
> 2) zones have to start and end at pfn:s that are a multiple of
> PAGE_SIZE
> 3) for sparsemem, the smallest section size is 1 << (PAGE_SIZE * 2).
Yeah, I've thought through some scenarios and I can't think of any where
it breaks unless the section size is really small, or a
non-power-of-two. But, I don't think it is as feasible for DISCONTIGMEM
or normal FLATMEM configurations.
-- Dave
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-02-09 17:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 6:46 Magnus Damm
2006-02-08 11:54 ` Nick Piggin
2006-02-09 2:35 ` Magnus Damm
2006-02-09 4:19 ` Nick Piggin
2006-02-09 5:19 ` Magnus Damm
2006-02-09 5:37 ` Nick Piggin
2006-02-11 5:30 ` Marcelo Tosatti
2006-02-10 15:03 ` Rik van Riel
2006-02-08 19:37 ` Dave Hansen
2006-02-09 2:50 ` Magnus Damm
2006-02-09 17:27 ` Dave Hansen [this message]
2006-02-09 1:55 ` KAMEZAWA Hiroyuki
2006-02-09 2:57 ` Magnus Damm
2006-02-09 3:14 ` KAMEZAWA Hiroyuki
2006-02-09 3:38 ` Magnus Damm
2006-02-09 3:51 ` KAMEZAWA Hiroyuki
2006-02-09 5:24 ` Magnus Damm
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=1139506075.9209.9.camel@localhost.localdomain \
--to=haveblue@us.ibm.com \
--cc=apw@shadowen.org \
--cc=damm@opensource.se \
--cc=linux-mm@kvack.org \
--cc=magnus.damm@gmail.com \
--cc=magnus@valinux.co.jp \
/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