public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Bob Picco <bob.picco@hp.com>
To: linux-ia64@vger.kernel.org
Subject: [PATCH 0/4] V4 ia64 SPARSEMEM
Date: Thu, 22 Sep 2005 16:14:18 +0000	[thread overview]
Message-ID: <20050922161418.GW16066@localhost.localdomain> (raw)

Tony,

This patchset differs very little from V3. It requires SPARSEMEM EXTREME
patches which are in 2.6.14-rcX.

ChangeLog V2:
	Jesse's review input has been applied to patches 3 and 4.
	These were all cosmetic changes.
ChangeLog V3:
	This patchset has changes for building ia64 with 
	ARCH_SPARSEMEM_EXTREME config options.  The configuration options
	SECTION_BITS and PHYSICAL_MEMORY_BITS have been removed.  I've
	chosen SECTION_SIZE_BITS to be 30. I'm sure this will be debated
	but seems adequate for the near term. 

	This patchset depends on SPARSEMEM EXTREME patch submitted to -mm.
	The -mm patch makes mem_section a one dimensional array of pointers 
	to mem_sections. The two level layout reduces the memory requirements
	of SPARSEMEM for very sparse memory but at the expense of an 
	additional shift and load instruction.

	The SPARSEMEM function memory_present, which marks sections with
	memory, is called from paging_init instead of find_memory. This is
	done because the bootmem allocator in used by SPARSEMEM to allocate
	the SPARSEMEM section arrays. This is the only code change within
	this patchset.
ChanageLog V4:
	SPARSEMEM EXTREME is now the default SPARSEMEM configuration. Thus
	the arch doesn't need to request EXTREME.  A couple of preprocessor
	#elif were cleaned up. There was a merge conflict in discontig.c's
	paging_init function and some minor code rearranging was required.

	Thanks to Kame and Yasunori for review and corrections.

	Memory models SPARSEMEM+EXTREME, DISCONTIG+VIRTUAL_MEM_MAP, 
	FLATMEM and FLATMEM+VIRTUAL_MEM_MAP were boot tested on rx2600
	by me; against -rcX.  Yasunori did the same configuration testing 
	on his Tiger4 box with Node emulation for NUMA; against -rc1.
	

thanks,

bob

             reply	other threads:[~2005-09-22 16:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-22 16:14 Bob Picco [this message]
2005-09-26 20:40 ` [PATCH 0/4] V4 ia64 SPARSEMEM Luck, Tony
2005-09-26 22:23 ` Luck, Tony
2005-09-26 23:35 ` Bob Picco
2005-09-26 23:40 ` Bob Picco
2005-09-27  0:03 ` Luck, Tony
2005-09-27  1:20 ` David Mosberger-Tang
2005-09-27  4:53 ` Yasunori Goto
2005-09-27 12:45 ` Jack Steiner
2005-09-27 14:09 ` Bob Picco
2005-09-27 14:10 ` Bob Picco
2005-09-27 19:22 ` Bob Picco
2005-09-27 22:00 ` Luck, Tony

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=20050922161418.GW16066@localhost.localdomain \
    --to=bob.picco@hp.com \
    --cc=linux-ia64@vger.kernel.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