Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (herse.apache.org: domain of liyilei1979@gmail.com
 designates 64.233.184.226 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=b49ppUs2LOcyTn2wHcDMSYAIJPY9z7KodCtGaLngi6krmk9lHslFnZoIQPUbEA7NCm3vXQfDqxO20Gl/fXnP5dHVU4co+AJGCDio7bZSoKGa79Dlnv/Vt+gTsvP0w/2QKHw2o5s0B72hJ2N7TlXJbHR1yrqc29QrS9E2wvgA8po=
Message-ID: <e66844de0702091649w433701d9qe43b58b460fa26d1@mail.gmail.com>
Date: Sat, 10 Feb 2007 08:49:10 +0800
From: "Leo Li" <liyilei1979@gmail.com>
To: dev@harmony.apache.org
Subject: Re: [VM]take action for native memory control (was: Re: [VM]How to
 trigue GC while free native memory is low.)
In-Reply-To: <51d555c70702090943i22445aeauabe78929f3a9c855@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_55153_32620050.1171068550428"
References: <5c8e69f0702090134j2e67b786v35e847e997d67dad@mail.gmail.com>
	 <51d555c70702090943i22445aeauabe78929f3a9c855@mail.gmail.com>

------=_Part_55153_32620050.1171068550428
Content-Type: text/plain; charset=ISO-2022-JP; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

  Good!
  I have just tried a memory resource monitor and it can be put as a part of
portlib to detect the current usage of memory usage.
  Maybe it can be the first step.:)

On 2/10/07, Rana Dasgupta <rdasgupt@gmail.com> wrote:
>
> The quick solution sounds great, thanks Jimmy. And opening the JIRA is the
> right thing to do.
>
> On 2/9/07, LvJimmy，Jing <firepure@gmail.com> wrote:
> >
> > Hi All,
> >    I open a new thread for this topic as I'd like to take action for
> > this. As RI behaves different from Harmony (it never throw that
> > memory-out-error), it should be a bug of Harmony and we should fix it,
> > so I open a JIRA, HARMONY-3148 to record this bug and action on it.
> >    Up to now, I see two kinds of solutions:
> >    One solution that is perfect to me is that modify current GC to
> > handle this native memory , it may use Java heap as native memory, or
> > try to control native memory as Java heap. But  IMHO, this may be a
> > long way to go to reach this target, requiring long discussion and
> > well-design for new GC(and VM).
> >    Other poor but quick solution is detect native memory usage in
> > classlib native code, and call System.gc() if necessary. This is a
> > fast fix and at least solve part of the problem. A little study on
> > this solution shows its feasibility and it may not require so much
> > work as the perfect solution.
> >    So I suggest patch our code with this quick solution in the while,
> > and if GC gets ready for the perfect solution, we remove this patch.
> > During this period, more discussion for the design are still welcomed.
> >     Any ideas/suggestions/comments? Thanks.
> >
> > --
> >
> > Best Regards!
> >
> > Jimmy, Jing Lv
> > China Software Development Lab, IBM
> >
>


-- 
Leo Li
China Software Development Lab, IBM

------=_Part_55153_32620050.1171068550428--