linux-kernel - Re: [PATCH v4 3/3] Doc/memory-barriers: Add Korean translation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160708101327.GB20765@gmail.com>
Date:	Fri, 8 Jul 2016 12:13:27 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Byungchul Park <byungchul.park@....com>
Cc:	SeongJae Park <sj38.park@...il.com>,
	Paul McKenney <paulmck@...ux.vnet.ibm.com>,
	David Howells <dhowells@...hat.com>,
	Minchan Kim <minchan@...nel.org>,
	Jonathan Corbet <corbet@....net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	linux-doc <linux-doc@...r.kernel.org>
Subject: Re: [PATCH v4 3/3] Doc/memory-barriers: Add Korean translation


* Byungchul Park <byungchul.park@....com> wrote:

> On Fri, Jul 08, 2016 at 07:50:39AM +0900, SeongJae Park wrote:
> > > I will add my opinion in korean.
> > 
> > Thank you for kind and faithful review.  I agree with most of your opinions and
> > suggestions.  Most of your suggestions looks much better than mine.
> > 
> > However, I also have some different opinion.  I want to emphasize the fact that
> > (1) CPUs 'issue' memory operations to memory system as they want, (2) memory
> > system 'executes' those operations as they want, and (3) CPUs 'perceive' the
> > 'effects' of the operation executions as they want.  I want to emphasize the
> > fact in document because I think most confusion about memory ordering comes
> > from vague understanding about the relation.  To my perspective, few of your
> 
> Right. I agree with you.

Do these vague formulations exist in the English text as well? If yes then please 
try to improve the English text first, then do the Korean translation.

Thanks,

	Ingo