public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: <linux-kernel@vger.kernel.org>, <linux-ia64@vger.kernel.org>,
	<lse-tech@lists.sourceforge.net>
Cc: <raybry@sgi.com>, "'Andy Whitcroft'" <apw@shadowen.org>,
	"Andrew Morton" <akpm@osdl.org>
Subject: hugetlb demand paging patch part [0/3]
Date: Tue, 13 Apr 2004 16:17:04 -0700	[thread overview]
Message-ID: <200404132317.i3DNH4F21162@unix-os.sc.intel.com> (raw)

In addition to the hugetlb commit handling that we've been working on
off the list, Ray Bryant of SGI and I are also working on demand paging
for hugetlb page.  Here are our final version that has been heavily
tested on ia64 and x86.  I've broken the patch into 3 pieces so it's
easier to read/review, etc.

1. hugetlb_fix_pte.patch - with demand paging, we can not unconditionally
   assume valid pmd/pte.  Fix it up in arch specific huge_pge_offset()
   and have all caller check the return value.

2. hugetlb_demand_generic.patch - this handles bulk of hugetlb demand
   paging for generic portion of the kernel.  I've put hugetlb fault
   handler in mm/hugetlbpage.c since the fault handler is *exactly* the
   same for all arch, but that requires opening up huge_pte_alloc() and
   set_huge_pte() functions in each arch.  If people object where it
   should live.  It takes me less than a minute to delete the common
   code and replicate it in each of the 5 arch that supports hugetlb.
   Just let me know if that's the case.

3. hugetlb_demand_arch.patch - this adds additional arch specific fixes
   for x84 and ia64 when generic demand paging is turned on.  Also bulk
   of the patch is to clean up with functions that no longer needed.

Some caveats:  I don't have sh and sparc64 hardware to test.  But hugetlb
code in these two arch looked like a triplet twin of x86 code.  So I'm
pretty sure it will work right out of box.  I've monkeyed around with
ppc64 code and after a while I realized it should be left for the experts.
I'm sure there are plenty ppc64 developers out there that can get it done
in no time.

Patches relative to linux-2.6.5-mm4 and on top of hugetlb overcommit
handling patch posted by Andy Whitcroft.

Andrew, would you please review and consider for -mm?  Thanks.

- Ken



             reply	other threads:[~2004-04-13 23:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-13 23:17 Chen, Kenneth W [this message]
2004-04-14  9:04 ` hugetlb demand paging patch part [0/3] Arjan van de Ven
2004-04-14 10:08   ` Andy Whitcroft
2004-04-14 15:21   ` [Lse-tech] " Martin J. Bligh
2004-04-14 15:23     ` Martin J. Bligh
2004-04-15  1:23   ` David Gibson
2004-04-15  6:42 ` David Gibson
2004-04-15 17:08   ` Chen, Kenneth W
2004-04-16  1:30     ` 'David Gibson'
2004-04-16  3:01       ` Chen, Kenneth W
2004-04-16  3:32         ` 'David Gibson'
2004-04-16  3:43           ` Chen, Kenneth W
2004-04-16  4:02             ` 'David Gibson'
     [not found] <7A4826DE8867D411BAB8009027AE9EB91DB42C83@scsmsx401.sc.intel.com>
2004-04-15 18:42 ` Chen, Kenneth W
2004-04-16  1:38   ` 'David Gibson'

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=200404132317.i3DNH4F21162@unix-os.sc.intel.com \
    --to=kenneth.w.chen@intel.com \
    --cc=akpm@osdl.org \
    --cc=apw@shadowen.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=raybry@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