Re: [REVISED DOC on v3] Crossrelease Lockdep

From	Byungchul Park <byungchul.park@lge.com>
Newsgroups	linux.kernel
Subject	Re: [REVISED DOC on v3] Crossrelease Lockdep
Date	2016-11-08 04:00 +0100
Message-ID	<sB4NH-3p8-9@gated-at.bofh.it> (permalink)
References	<sgSvL-8uI-5@gated-at.bofh.it> <syWAV-27V-3@gated-at.bofh.it> <szlzk-1qz-9@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Thu, Nov 03, 2016 at 05:18:13PM +0900, Byungchul Park wrote:
> Hello Peterz,
> 
> I tried to explain about what you asked me for.
> I wonder if I did it exactly. But I hope so.
> Please let me know if there's something more I need to add.

Just to be sure, are you concerning about sync and propagation delay of
memory contents including lock variables between cpus?

IMHO, it makes no difference. It's a true dependence once the dependency
is viewable by a cpu, which means anyway it actually happened. And please
remind all locks related to crosslocks are serialized via proper memory
barriers. I think this was already descibed in my document.

Is there something I missed? Please let me know.

Thank you,
Byungchul

> 
> Thank you,
> Byungchul

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

[REVISED DOC on v3] Crossrelease Lockdep Byungchul Park <byungchul.park@lge.com> - 2016-11-02 06:50 +0100
  Re: [REVISED DOC on v3] Crossrelease Lockdep Byungchul Park <byungchul.park@lge.com> - 2016-11-03 09:30 +0100
    Re: [REVISED DOC on v3] Crossrelease Lockdep Byungchul Park <byungchul.park@lge.com> - 2016-11-08 04:00 +0100

csiph-web