Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (athena.apache.org: domain of icyrong@gmail.com designates
 209.85.198.189 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=lLwRFzRWQ8izmgYc0BSWx9qBF9L4SUJBVuEKEQne/YGQV9dQdddIv/DUhsACSawTW7Y1ob7RBXmo7AtbxCn9c8xfSo6UPtRbBaplYVFFyzQQ5zsgqDYm4vonL27TfuUMvNQN4arzi5z+fpqBObQx93dWDg7gUPA/Y8Ilzfiv9Hc=
Message-ID: <b8ed57860712142233s69741d35yf43a2bcdf8a0a280@mail.gmail.com>
Date: Sat, 15 Dec 2007 14:33:13 +0800
From: "=?GB2312?B?yrezycjZ?=" <icyrong@gmail.com>
To: dev@harmony.apache.org
Subject: Re: [drlvm][jitrino]
In-Reply-To: <9623c9a50712140100u6cd09712oef1cf1d2557623a9@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_3534_27152966.1197700393635"
References: <b8ed57860712132357p2796a78cxc932bfa83f10bf9@mail.gmail.com>
	 <9623c9a50712140100u6cd09712oef1cf1d2557623a9@mail.gmail.com>

------=_Part_3534_27152966.1197700393635
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I still have 2 questions.

First, I know in the Thread Manager, it is the
hythread_thin_monitor_try_enter method to aquire the mutex lock
and implement the *memory barrier.* But* *I looked into the code of this
method, didn't find any memory barrier operations(including the
apr_memory_rw_barrier() call and  cmpxchg operation) when it is the fat
lock. when aquiring the fat lock, it calls the hythread_monitor_try_enter
method. In the hythread_monitor_try_enter method* there isn't *memory
barrier operations, but has a call of the *hymutex_trylock* method. Does the
hymutex_trylock method also has barrier effect built-in?

Second, when exit the synchoronized area, it should release the mutex lock
and flush the local memory to the main memory. But the
hythread_thin_monitor_exit method only release the mutex lock and I don't
find any flushing operation in hythread_thin_monitor_exit method.

I think there must be some mistakes of my idea, hoping for your advice.


>  Thanks,
>  Chengrong
>
>
>
>

------=_Part_3534_27152966.1197700393635--