From: Andrew Morton <akpm@osdl.org>
To: Andy Whitcroft <apw@shadowen.org>
Cc: kenneth.w.chen@intel.com, raybry@sgi.com, 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 22:47:42 +0000 [thread overview]
Message-ID: <20040408154742.3faf7141.akpm@osdl.org> (raw)
In-Reply-To: <15037082.1081445730@42.150.104.212.access.eclipse.net.uk>
Andy Whitcroft <apw@shadowen.org> wrote:
>
> We have been looking at the HUGETLB page commit issue (offlist) and are
> close a final merged patch.
Be aware that I've merged a patch from Bill which does all the hugetlb code
unduplication. A thousand lines gone:
25-akpm/arch/i386/mm/hugetlbpage.c | 264 ----------------------------------
25-akpm/arch/ia64/mm/hugetlbpage.c | 251 --------------------------------
25-akpm/arch/ppc64/mm/hugetlbpage.c | 257 ---------------------------------
25-akpm/arch/sh/mm/hugetlbpage.c | 258 ---------------------------------
25-akpm/arch/sparc64/mm/hugetlbpage.c | 259 ---------------------------------
25-akpm/fs/hugetlbfs/inode.c | 2
25-akpm/include/linux/hugetlb.h | 7
25-akpm/kernel/sysctl.c | 6
25-akpm/mm/Makefile | 1
25-akpm/mm/hugetlb.c | 245 +++++++++++++++++++++++++++++++
10 files changed, 263 insertions(+), 1287 deletions(-)
Of course, this buggers up everyone else's patches, but I do think this
work has to come first.
I still need to test this on ppc64 and ia64. I've dropped a rollup against
2.6.5 at http://www.zip.com.au/~akpm/linux/patches/stuff/mc3.bz2 which you
should work against until I get -mc3 out for real.
next prev parent reply other threads:[~2004-04-08 22:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 16:35 HUGETLB commit handling Andy Whitcroft
2004-04-08 21:58 ` Seth, Rohit
2004-04-08 22:47 ` Andrew Morton [this message]
2004-04-13 10:20 ` Andy Whitcroft
[not found] <1IKJu-Zn-29@gated-at.bofh.it>
2004-04-08 17:05 ` Andi Kleen
2004-04-08 17:23 ` Ray Bryant
2004-04-08 17:51 ` Andi Kleen
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=20040408154742.3faf7141.akpm@osdl.org \
--to=akpm@osdl.org \
--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