From: tip-bot for SeongJae Park <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
will.deacon@arm.com, sj38.park@gmail.com, hpa@zytor.com,
akpm@linux-foundation.org, paulmck@linux.vnet.ibm.com,
peterz@infradead.org, torvalds@linux-foundation.org,
mingo@kernel.org
Subject: [tip:locking/core] locking/memory-barriers.txt/kokr: Update Korean translation to de-emphasize smp_read_barrier_depends()
Date: Mon, 14 May 2018 23:22:49 -0700 [thread overview]
Message-ID: <tip-1ea32723c42a5c73a6da6a9731b9bdb6c5f206f0@git.kernel.org> (raw)
In-Reply-To: <1526338533-6044-3-git-send-email-paulmck@linux.vnet.ibm.com>
Commit-ID: 1ea32723c42a5c73a6da6a9731b9bdb6c5f206f0
Gitweb: https://git.kernel.org/tip/1ea32723c42a5c73a6da6a9731b9bdb6c5f206f0
Author: SeongJae Park <sj38.park@gmail.com>
AuthorDate: Mon, 14 May 2018 15:55:28 -0700
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Tue, 15 May 2018 08:11:14 +0200
locking/memory-barriers.txt/kokr: Update Korean translation to de-emphasize smp_read_barrier_depends()
Translate this commit to Korean:
9ad3c143d7d6 ("doc: De-emphasize smp_read_barrier_depends")
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Will Deacon <will.deacon@arm.com>
Cc: akiyks@gmail.com
Cc: boqun.feng@gmail.com
Cc: dhowells@redhat.com
Cc: j.alglave@ucl.ac.uk
Cc: linux-arch@vger.kernel.org
Cc: luc.maranget@inria.fr
Cc: npiggin@gmail.com
Cc: parri.andrea@gmail.com
Cc: stern@rowland.harvard.edu
Link: http://lkml.kernel.org/r/1526338533-6044-3-git-send-email-paulmck@linux.vnet.ibm.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
Documentation/translations/ko_KR/memory-barriers.txt | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/Documentation/translations/ko_KR/memory-barriers.txt b/Documentation/translations/ko_KR/memory-barriers.txt
index edef154d77b2..44e47c2d33cf 100644
--- a/Documentation/translations/ko_KR/memory-barriers.txt
+++ b/Documentation/translations/ko_KR/memory-barriers.txt
@@ -1790,7 +1790,7 @@ CPU 메모리 배리어
범용 mb() smp_mb()
쓰기 wmb() smp_wmb()
읽기 rmb() smp_rmb()
- 데이터 의존성 read_barrier_depends() smp_read_barrier_depends()
+ 데이터 의존성 READ_ONCE()
데이터 의존성 배리어를 제외한 모든 메모리 배리어는 컴파일러 배리어를
@@ -2829,7 +2829,10 @@ CPU 2 는 C/D 를 갖습니다)가 병렬로 연결되어 있는 시스템을
다른 CPU 들도 분할된 캐시를 가지고 있을 수 있지만, 그런 CPU 들은 평범한 메모리
액세스를 위해서도 이 분할된 캐시들 사이의 조정을 해야만 합니다. Alpha 는 가장
약한 메모리 순서 시맨틱 (semantic) 을 선택함으로써 메모리 배리어가 명시적으로
-사용되지 않았을 때에는 그런 조정이 필요하지 않게 했습니다.
+사용되지 않았을 때에는 그런 조정이 필요하지 않게 했으며, 이는 Alpha 가 당시에
+더 높은 CPU 클락 속도를 가질 수 있게 했습니다. 하지만, Alpha 아키텍쳐 전용
+코드와 READ_ONCE() 매크로 내부에서를 제외하고는 smp_read_barrier_depends() 가
+사용되지 않아야 함을 알아두시기 바랍니다.
캐시 일관성 VS DMA
next prev parent reply other threads:[~2018-05-15 6:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 22:54 [PATCH memory-model 0/8] memory-barriers.txt and atomic_ops.rst updates Paul E. McKenney
2018-05-14 22:55 ` [PATCH memory-model 1/8] docs/memory-barriers.txt: Fix broken DMA vs MMIO ordering example Paul E. McKenney
2018-05-15 6:21 ` [tip:locking/core] locking/memory-barriers.txt: Fix broken DMA vs. " tip-bot for Will Deacon
2018-05-14 22:55 ` [PATCH memory-model 2/8] kokr/doc: READ_ONCE() now implies smp_barrier_depends() Paul E. McKenney
2018-05-15 6:22 ` [tip:locking/core] locking/memory-barriers.txt/kokr: Update Korean translation to indicate that " tip-bot for SeongJae Park
2018-05-14 22:55 ` [PATCH memory-model 3/8] kokr/doc: De-emphasize smp_read_barrier_depends Paul E. McKenney
2018-05-15 6:22 ` tip-bot for SeongJae Park [this message]
2018-05-14 22:55 ` [PATCH memory-model 4/8] kokr/Documentation/memory-barriers.txt: Cross-reference "tools/memory-model/" Paul E. McKenney
2018-05-15 6:23 ` [tip:locking/core] locking/memory-barriers.txt/kokr: Update Korean translation to cross-reference "tools/memory-model/" tip-bot for SeongJae Park
2018-05-14 22:55 ` [PATCH memory-model 5/8] kokr/memory-barriers: Fix description of data dependency barriers Paul E. McKenney
2018-05-15 6:23 ` [tip:locking/core] locking/memory-barriers.txt/kokr: Update Korean translation to fix " tip-bot for SeongJae Park
2018-05-14 22:55 ` [PATCH memory-model 6/8] kokr/locking/memory-barriers: De-emphasize smp_read_barrier_depends() some more Paul E. McKenney
2018-05-15 6:24 ` [tip:locking/core] locking/memory-barriers.txt/kokr: Update Korean translation to de-emphasize " tip-bot for SeongJae Park
2018-05-14 22:55 ` [PATCH memory-model 7/8] atomic_ops.rst: Fix wrong example code Paul E. McKenney
2018-05-15 6:24 ` [tip:locking/core] locking/Documentation: Fix incorrect " tip-bot for SeongJae Park
2018-05-14 22:55 ` [PATCH memory-model 8/8] atomic_ops.rst: Use `warning` rst directive Paul E. McKenney
2018-05-15 6:25 ` [tip:locking/core] locking/Documentation: Use `warning` RST directive tip-bot for SeongJae Park
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=tip-1ea32723c42a5c73a6da6a9731b9bdb6c5f206f0@git.kernel.org \
--to=tipbot@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=sj38.park@gmail.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.com \
/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;
as well as URLs for NNTP newsgroup(s).