From: Andi Kleen <ak@muc.de>
To: Andy Whitcroft <apw@shadowen.org>
Cc: "Chen, Kenneth W" <kenneth.w.chen@intel.com>,
'Ray Bryant' <raybry@sgi.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:05:40 +0000 [thread overview]
Message-ID: <m3u0zuwgbf.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <1IKJu-Zn-29@gated-at.bofh.it> (Andy Whitcroft's message of "Thu, 08 Apr 2004 18:40:12 +0200")
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
next parent reply other threads:[~2004-04-08 17:05 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 ` Andi Kleen [this message]
2004-04-08 17:23 ` HUGETLB commit handling Ray Bryant
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=m3u0zuwgbf.fsf@averell.firstfloor.org \
--to=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=raybry@sgi.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