public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Ray Bryant <raybry@sgi.com>
To: Andi Kleen <ak@muc.de>
Cc: Andy Whitcroft <apw@shadowen.org>,
	"Chen, Kenneth W" <kenneth.w.chen@intel.com>,
	"Martin J. Bligh" <mbligh@aracnet.com>,
	linux-kernel@vger.kernel.org, anton@samba.org,
	sds@epoch.ncsc.mil, ak@suse.de, lse-tech@lists.sourceforge.net,
	linux-ia64@vger.kernel.org
Subject: Re: HUGETLB commit handling.
Date: Thu, 08 Apr 2004 17:23:00 +0000	[thread overview]
Message-ID: <40758A74.3040107@sgi.com> (raw)
In-Reply-To: <m3u0zuwgbf.fsf@averell.firstfloor.org>

Andi,

Yes, that is the plan we are heading for.  However, to make things simpler and 
follow the "subnit a patch that does one thing" rule, we will likely do two 
patches, one to add hugetlb commit handling, and a second one to add lazy 
allocation for i386 and IA64.

The other problem we are wrestling with is how to do the ia386 and ia64 lazy 
allocation code without breaking the architectures that haven't yet switched 
to lazy allocation.  There will probbaly be some

#define ARCH_USES_HUGETLB_PREFAULT

nonsense added to deal with the latter, if needed.

Then, further down the road, we'd like to get the common code across 
architectures moved up from arch/mm to mm.

Andi Kleen wrote:
> Andy Whitcroft <apw@shadowen.org> writes:
> 
> 
>>We have been looking at the HUGETLB page commit issue (offlist) and are
>>close a final merged patch.  However, our testing seems to have thrown up
> 
> 
> This includes lazy allocation for i386 and IA64, right?
> 
> If yes, I'm waiting for your final patch then to remerge the NUMA
> policy code into it (currently NUMA API contains a dumb version of lazy
> allocation for i386 without any prereservation)
> 
> 
>>I would contend this is the right thing to do, as it makes the semantics of
>>hugepages match that of the existing small pages.  We are looking for a
>>consensus as this might be construed as a semantic change.
> 
> 
> I think it's more clean to do it at shmget() time too, so it's probably the
> right thing to do.
> 
> -Andi
> 
> 

-- 
Best Regards,
Ray
-----------------------------------------------
                   Ray Bryant
512-453-9679 (work)         512-507-7807 (cell)
raybry@sgi.com             raybry@austin.rr.com
The box said: "Requires Windows 98 or better",
            so I installed Linux.
-----------------------------------------------


  reply	other threads:[~2004-04-08 17:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1IKJu-Zn-29@gated-at.bofh.it>
2004-04-08 17:05 ` HUGETLB commit handling Andi Kleen
2004-04-08 17:23   ` Ray Bryant [this message]
2004-04-08 17:51     ` Andi Kleen
2004-04-08 16:35 Andy Whitcroft
2004-04-08 21:58 ` Seth, Rohit
2004-04-08 22:47 ` Andrew Morton
2004-04-13 10:20   ` Andy Whitcroft

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=40758A74.3040107@sgi.com \
    --to=raybry@sgi.com \
    --cc=ak@muc.de \
    --cc=ak@suse.de \
    --cc=anton@samba.org \
    --cc=apw@shadowen.org \
    --cc=kenneth.w.chen@intel.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=mbligh@aracnet.com \
    --cc=sds@epoch.ncsc.mil \
    /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