Received: by 2002:a05:6358:1087:b0:cb:c9d3:cd90 with SMTP id j7csp1646305rwi; Mon, 10 Oct 2022 20:44:31 -0700 (PDT) X-Google-Smtp-Source: AMsMyM6sBttku15wMi/457cy5FDLb4E9kB+8BPIED8uh6KMS4bZMogv3m+7G6SJMqifJXz9b5foe X-Received: by 2002:aa7:dd57:0:b0:453:2d35:70bb with SMTP id o23-20020aa7dd57000000b004532d3570bbmr20930070edw.26.1665459871774; Mon, 10 Oct 2022 20:44:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1665459871; cv=none; d=google.com; s=arc-20160816; b=rnN7nHvB+9pxWDmoyk+6AwxVo9ytEjCJv8zUNpkfIbwH2S0b6rrB5bSznLz1RX9XX7 Td3s8+DKMBKZZLv6HxitUq9SL0/XoNi1/DLgebnIC3yFESM6ELdw+f/KxIrDqXkOnI12 CdLv5fZaggcEnoedy7ktQxmT4NveuSF3MwVsVoQt2Brw42ex6KaXUKkFpsDow5grirtP ljLWeVt53p5hagBrJiHqOjTaQr6jsFoejV4dpl1SeR7hzROrez93e8gWIp/u6KMwyG4Q vNvnZ3BzVoPy5Um9LtTApqu90Xzh3pPm1e0Foe68YEglE76HNW6YUgAaPPTWWArW7MhA Vr7Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=KnzRDiSO4h9grjbrjzEwaGTpGjXiNK7uLh2e/CxiMig=; b=Y0Ll1SUQ2Qvai9Z1IKOuvAEJ+q1IwPuQqA2OD52aqJjLLaIYdUIW7cmNb27MMQSxVR 27ScP97Ya9K+OFDeEaKy+vehEedMZdMXUHYYuFcs3+TIA19d2gBzLQUEv7eb6eG66l2a BgTgEyCjmwnBFebJeLt2/9nx+Zz5LsBrh07VyWHiB65drwujYcHB56l6+hT/zQ49EvKL aQldAfoPVX4wVKZsDYLfLKkHkmdMeDF/Z7chdRooPcEGePkme71U2XWQ3PapUCuVGFye dq37mrwGCgARb3WTqnMvGsCjzyLUGP36cdCAbiSNmeVX6hpEvkL07HHfh1ekO/jIbYKe b8+g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=SiHYR+Ee; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id xg7-20020a170907320700b0078333d9f17bsi13661342ejb.819.2022.10.10.20.44.05; Mon, 10 Oct 2022 20:44:31 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=SiHYR+Ee; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229889AbiJKC6j (ORCPT + 99 others); Mon, 10 Oct 2022 22:58:39 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56868 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229893AbiJKC6h (ORCPT ); Mon, 10 Oct 2022 22:58:37 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 78E1A5F9B7; Mon, 10 Oct 2022 19:58:36 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 0E6EE6108D; Tue, 11 Oct 2022 02:58:36 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5392AC433D7; Tue, 11 Oct 2022 02:58:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1665457115; bh=aVcrvy3o9Fi5GQp2mJLQFTz455k5JRw2I8ApU+G0WYU=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=SiHYR+EeC9KxjObqw1vuvNPclsCTCh6KcNNpQ3CMsRcTEVD0vBVlDiCP08SwFP28C WNFvD1YqoyT3FQVlmu4DbV2P2jNIsqImdDEev/9Ty5Ng0WAclmeQ1rXveUGs+olRrt 6LsvhcW0fYa9ByAsA6qVMaJlXF6bPAI7uhWpME18MDZ4g1OQwKaqdkps++61lF1c3L VYnUbgt7iEEyFsUARTTFGdQEFKgV0hTU6OGkPESNvDuk39QFiAN9dfiAm0/pHZ8XWX m+krQ1NRAwRLWUj4LVeHQVQoidTq50Zzl2hY6jaPx0GGW6qDGzt/2FaSyTQzBoXLeO eEIA1/SRKWSIQ== From: SeongJae Park To: paulmck@kernel.org, corbet@lwn.net Cc: lyj7694@gmail.com, linux-doc@vger.kernel.org, linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, SeongJae Park Subject: [PATCH v2 2/3] docs/memory-barriers.txt/kokr: Add memory barrier dma_mb() Date: Mon, 10 Oct 2022 19:58:08 -0700 Message-Id: <20221011025809.25821-3-sj@kernel.org> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20221011025809.25821-1-sj@kernel.org> References: <20221011025809.25821-1-sj@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Translate this commit to Korean: ed59dfd9509d ("asm-generic: Add memory barrier dma_mb()") Signed-off-by: SeongJae Park --- .../translations/ko_KR/memory-barriers.txt | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/Documentation/translations/ko_KR/memory-barriers.txt b/Documentation/translations/ko_KR/memory-barriers.txt index 96b4162989a0..38656f6680e2 100644 --- a/Documentation/translations/ko_KR/memory-barriers.txt +++ b/Documentation/translations/ko_KR/memory-barriers.txt @@ -1863,6 +1863,7 @@ Mandatory 배리어들은 SMP 시스템에서도 UP 시스템에서도 SMP 효 (*) dma_wmb(); (*) dma_rmb(); + (*) dma_mb(); 이것들은 CPU 와 DMA 가능한 디바이스에서 모두 액세스 가능한 공유 메모리의 읽기, 쓰기 작업들의 순서를 보장하기 위해 consistent memory 에서 사용하기 @@ -1893,12 +1894,13 @@ Mandatory 배리어들은 SMP 시스템에서도 UP 시스템에서도 SMP 효 dma_rmb() 는 디스크립터로부터 데이터를 읽어오기 전에 디바이스가 소유권을 내려놓았을 것을 보장하고, dma_wmb() 는 디바이스가 자신이 소유권을 다시 - 가졌음을 보기 전에 디스크립터에 데이터가 쓰였을 것을 보장합니다. 참고로, - writel() 을 사용하면 캐시 일관성이 있는 메모리 (cache coherent memory) - 쓰기가 MMIO 영역에의 쓰기 전에 완료되었을 것을 보장하므로 writel() 앞에 - wmb() 를 실행할 필요가 없음을 알아두시기 바랍니다. writel() 보다 비용이 - 저렴한 writel_relaxed() 는 이런 보장을 제공하지 않으므로 여기선 사용되지 - 않아야 합니다. + 가졌음을 보기 전에 디스크립터에 데이터가 쓰였을 것을 보장합니다. dma_mb() + 는 dma_rmb() 와 dma_wmb() 를 모두 내포합니다. 참고로, writel() 을 + 사용하면 캐시 일관성이 있는 메모리 (cache coherent memory) 쓰기가 MMIO + 영역에의 쓰기 전에 완료되었을 것을 보장하므로 writel() 앞에 wmb() 를 + 실행할 필요가 없음을 알아두시기 바랍니다. writel() 보다 비용이 저렴한 + writel_relaxed() 는 이런 보장을 제공하지 않으므로 여기선 사용되지 않아야 + 합니다. writel_relaxed() 와 같은 완화된 I/O 접근자들에 대한 자세한 내용을 위해서는 "커널 I/O 배리어의 효과" 섹션을, consistent memory 에 대한 자세한 내용을 -- 2.17.1