From: Dave Hansen <haveblue@us.ibm.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Andrew Morton <akpm@osdl.org>,
linux-arch@vger.kernel.org, Andy Whitcroft <apw@shadowen.org>,
Matt Tolentino <matthew.e.tolentino@intel.com>,
Bob Picco <bob.picco@hp.com>
Subject: Re: sparsemem patches in -mm
Date: Thu, 23 Jun 2005 15:56:13 -0700 [thread overview]
Message-ID: <1119567373.6694.15.camel@localhost> (raw)
In-Reply-To: <42BB3C26.6000603@linux-m68k.org>
On Fri, 2005-06-24 at 00:48 +0200, Roman Zippel wrote:
> Andrew Morton wrote:
> > Could I ask the arch maintainers to review the `sparsemem' patches from -mm,
> > please, if you haven't done so...
>
> They would need a bit more work to be usable on m68k. I have a basic
> patch to use DISCONTIGMEM for m68k. There I have the problem that I have
> to deal with almost random memory configurations. So converting a
> virtual/physical address or pfn into a section number can't use a
> compile time constant, instead an offset/shift is calculated at boot
> time and patched into the kernel.
As far as the shift, you can simply use the smallest possible size as
the SECTION_SIZE.
Nothing I can think of with sparsemem requires you to have the kernel be
at pfn 0. Unless you start at some completely huge address or have an
exceedingly low SECTION_SIZE, everything should fit. Remember,
sparsemem doesn't deal with virt/phys layout, just converting pfns to
and from pages.
If you want to mail me, or take this to your arch's list, we can
probably discuss more of the specifics for your arch.
-- Dave
next prev parent reply other threads:[~2005-06-23 22:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 9:13 sparsemem patches in -mm Andrew Morton
2005-06-21 9:50 ` Andi Kleen
2005-06-21 10:09 ` Andrew Morton
2005-06-21 15:49 ` Andy Whitcroft
2005-06-21 15:58 ` Andi Kleen
2005-06-21 11:00 ` Bob Picco
2005-06-21 15:57 ` Dave Hansen
2005-06-21 16:45 ` Bob Picco
2005-06-21 14:17 ` Matthew Wilcox
2005-06-21 15:51 ` Andy Whitcroft
2005-06-21 20:01 ` Andrew Morton
2005-06-21 23:39 ` Dave Hansen
2005-06-22 5:46 ` David S. Miller
2005-06-22 6:00 ` Andrew Morton
2005-07-27 22:42 ` David S. Miller
2005-06-23 22:48 ` Roman Zippel
2005-06-23 22:56 ` Dave Hansen [this message]
2005-06-23 23:53 ` Roman Zippel
-- strict thread matches above, loose matches on Subject: below --
2005-06-21 15:52 Luck, Tony
2005-06-21 15:58 ` Andy Whitcroft
2005-06-21 16:09 Luck, Tony
2005-06-21 16:17 ` Dave Hansen
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=1119567373.6694.15.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=bob.picco@hp.com \
--cc=linux-arch@vger.kernel.org \
--cc=matthew.e.tolentino@intel.com \
--cc=zippel@linux-m68k.org \
/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