mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Shi <alex.shi@intel.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Chen, Tim C" <tim.c.chen@intel.com>,
	"Zhang, Yanmin" <yanmin.zhang@intel.com>
Subject: Re: [patch] fix hugepage unuseable issu on non-NUMA machine
Date: Thu, 02 Jul 2009 10:05:35 +0800	[thread overview]
Message-ID: <1246500335.3042.28.camel@alexs-hp> (raw)
In-Reply-To: <4A4BA71C.8000509@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 683 bytes --]

Attachments are the kernel config file and the dmesg contents after
apply your patch. 

I tried to fire a bug on kernel bugzilla, But Andrew said e-mail is
better for this kind of bug. So let's track it via e-mail. 

BRG
Alex 

On Thu, 2009-07-02 at 02:12 +0800, Yinghai Lu wrote:
> Alex Shi wrote:
> > I have tried your patch. the specjbb2005 still can not run with the
> > following parameters under jrockit-R27.3.1-jre1.5.0_11 and with totla
> > 2GB hugepage memory setting. 
> > JAVA_OPTION= -Xmx2g -Xms2g -Xns1g -XXaggressive -Xlargepages -XXlazyUnlocking -Xgc:genpar -XXtlasize:min=16k,preferred=64k  -Djava.awt.headless=true
> 
> can you send out .config and bootlog?
> 
> YH

[-- Attachment #2: config-31-rc1.gz --]
[-- Type: application/x-gzip, Size: 15553 bytes --]

[-- Attachment #3: dmesg-yinghai.gz --]
[-- Type: application/x-gzip, Size: 11002 bytes --]

      reply	other threads:[~2009-07-02  2:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29 11:10 alex.shi
2009-06-29 17:01 ` Yinghai Lu
2009-07-01  9:38   ` Alex Shi
2009-07-01 18:12     ` Yinghai Lu
2009-07-02  2:05       ` Alex Shi [this message]

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=1246500335.3042.28.camel@alexs-hp \
    --to=alex.shi@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tim.c.chen@intel.com \
    --cc=yanmin.zhang@intel.com \
    --cc=yinghai@kernel.org \
    /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®