From: Anton Blanchard <anton@samba.org>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: David Gibson <david@gibson.dropbear.id.au>,
linux-kernel@vger.kernel.org, linuxppc64-dev@ozlabs.org,
Adam Litke <agl@us.ibm.com>, Andy Whitworth <apw@shadowen.org>
Subject: Re: [RFC] Consolidate lots of hugepage code
Date: Mon, 8 Nov 2004 08:22:12 +1100 [thread overview]
Message-ID: <20041107212212.GD16976@krispykreme.ozlabs.ibm.com> (raw)
In-Reply-To: <20041107210943.GN2890@holomorphy.com>
> On Mon, Nov 08, 2004 at 06:30:07AM +1100, Anton Blanchard wrote:
> > OK. We have not seen a similar issue on ppc64 even with extensive
> > testing (although with HPC apps). The question is how long we should
> > hold off on further hugetlb development waiting for this one bug report
> > on a single architecture to be chased.
>
> Until it's fixed. Until then I'm considering it a byproduct of that same
> development. And with your report, that makes it two architectures, not
> one.
We _arent_ seeing it on ppc64. Can we at least have a complete bug
report if we are to halt all hugetlb development? At the moment we dont
have much information to go on at all.
Anton
next prev parent reply other threads:[~2004-11-07 21:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 3:37 David Gibson
2004-10-29 3:48 ` William Lee Irwin III
2004-11-07 17:20 ` Anton Blanchard
2004-11-07 19:20 ` William Lee Irwin III
2004-11-07 19:30 ` Anton Blanchard
2004-11-07 21:09 ` William Lee Irwin III
2004-11-07 21:22 ` Anton Blanchard [this message]
2004-11-07 22:49 ` William Lee Irwin III
2004-11-20 15:38 ` Anton Blanchard
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=20041107212212.GD16976@krispykreme.ozlabs.ibm.com \
--to=anton@samba.org \
--cc=agl@us.ibm.com \
--cc=apw@shadowen.org \
--cc=david@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=wli@holomorphy.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
all inboxes | Powered by JetHome®