From: Andi Kleen <ak@muc.de>
To: Ray Bryant <raybry@sgi.com>
Cc: Andi Kleen <ak@muc.de>, 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:51:26 +0000 [thread overview]
Message-ID: <20040408175126.GA72736@colin2.muc.de> (raw)
In-Reply-To: <40758A74.3040107@sgi.com>
> 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.
In my patch I just used weak functions: use a dummy weak function
in the high level code and overwrite from the architecture specific
code as needed. This avoids all the ifdefs.
-Andi
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <ak@muc.de>
To: Ray Bryant <raybry@sgi.com>
Cc: Andi Kleen <ak@muc.de>, 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: 8 Apr 2004 19:51:26 +0200
Date: Thu, 8 Apr 2004 19:51:26 +0200 [thread overview]
Message-ID: <20040408175126.GA72736@colin2.muc.de> (raw)
In-Reply-To: <40758A74.3040107@sgi.com>
> 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.
In my patch I just used weak functions: use a dummy weak function
in the high level code and overwrite from the architecture specific
code as needed. This avoids all the ifdefs.
-Andi
next prev parent reply other threads:[~2004-04-08 17:51 UTC|newest]
Thread overview: 14+ 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:05 ` Andi Kleen
2004-04-08 17:23 ` Ray Bryant
2004-04-08 17:23 ` Ray Bryant
2004-04-08 17:51 ` Andi Kleen [this message]
2004-04-08 17:51 ` Andi Kleen
2004-04-08 16:35 Andy Whitcroft
2004-04-08 16:35 ` Andy Whitcroft
2004-04-08 21:58 ` Seth, Rohit
2004-04-08 21:58 ` Seth, Rohit
2004-04-08 22:47 ` Andrew Morton
2004-04-08 22:47 ` Andrew Morton
2004-04-13 10:20 ` Andy Whitcroft
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=20040408175126.GA72736@colin2.muc.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.