From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 38275C7115B for ; Thu, 26 Jun 2025 07:21:08 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id C04196B00B5; Thu, 26 Jun 2025 03:21:07 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id BDBB56B00B7; Thu, 26 Jun 2025 03:21:07 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id AF1336B00B9; Thu, 26 Jun 2025 03:21:07 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0016.hostedemail.com [216.40.44.16]) by kanga.kvack.org (Postfix) with ESMTP id 9FD3A6B00B5 for ; Thu, 26 Jun 2025 03:21:07 -0400 (EDT) Received: from smtpin12.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay04.hostedemail.com (Postfix) with ESMTP id 4CF901A0908 for ; Thu, 26 Jun 2025 07:21:07 +0000 (UTC) X-FDA: 83596705374.12.860EFFD Received: from mailout2.w1.samsung.com (mailout2.w1.samsung.com [210.118.77.12]) by imf06.hostedemail.com (Postfix) with ESMTP id B1AA818000C for ; Thu, 26 Jun 2025 07:21:04 +0000 (UTC) Authentication-Results: imf06.hostedemail.com; dkim=pass header.d=samsung.com header.s=mail20170921 header.b=UmJM2otD; spf=pass (imf06.hostedemail.com: domain of m.szyprowski@samsung.com designates 210.118.77.12 as permitted sender) smtp.mailfrom=m.szyprowski@samsung.com; dmarc=pass (policy=none) header.from=samsung.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1750922465; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=LPimFjjxe7jfdwBjYJXhsorVGtUpD3BI2ZbS3ELJhYk=; b=3x+R6oTqUiO9yLWgLBgW3kQGpG2B1TrssIr3BBuLjTmU8AbYdJJTM6dMhDxMizQnTjRkvE Jmwqfqwk4TBL4uJW3bbv8C2G3acLXdab6F7dBGoB9mTL0UpmYa2YuDXCjFbwxa9NDeVHSb MHYDy4Mdx3cdg+lAXjYJGCFI3h5Yx4o= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1750922465; a=rsa-sha256; cv=none; b=s32FfLTpKbgmubrHqbhtFkyd8XJ8Ugu4uOCl60uG6+1z2++DAVOXMiwvYAsZR0PdEQtMmn BFeFKYqtEySJEjTvovAf2qj0hyy9wPlM97FM9PYBGbDOfePfBtJNwEUOzIFjvTGuFdc/2S JYNnDaOzO1g9zYidhKDvkM/deOw2gWc= ARC-Authentication-Results: i=1; imf06.hostedemail.com; dkim=pass header.d=samsung.com header.s=mail20170921 header.b=UmJM2otD; spf=pass (imf06.hostedemail.com: domain of m.szyprowski@samsung.com designates 210.118.77.12 as permitted sender) smtp.mailfrom=m.szyprowski@samsung.com; dmarc=pass (policy=none) header.from=samsung.com Received: from eucas1p1.samsung.com (unknown [182.198.249.206]) by mailout2.w1.samsung.com (KnoxPortal) with ESMTP id 20250626072102euoutp02b891d8420542e8aadc974a6bc3edd478~MhrPus05E0849208492euoutp02F for ; Thu, 26 Jun 2025 07:21:02 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 mailout2.w1.samsung.com 20250626072102euoutp02b891d8420542e8aadc974a6bc3edd478~MhrPus05E0849208492euoutp02F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsung.com; s=mail20170921; t=1750922462; bh=LPimFjjxe7jfdwBjYJXhsorVGtUpD3BI2ZbS3ELJhYk=; h=Date:Subject:To:Cc:From:In-Reply-To:References:From; b=UmJM2otDrqRpBzvO2qj99Ds4/cZ0bS9VDuqkdaaSi1UUfpRMRFQlRdRF0rircsutJ p5YlojDXfZA2+rw9jdxegvh60GGV1UhpS0IrZN1g2GhQWjlqt9GAcAhXmQPLU2x4vq fpJ1B/WFbK3MxgwHzhZ8F3/ROYC1+69fnBMm5Ft4= Received: from eusmtip1.samsung.com (unknown [203.254.199.221]) by eucas1p1.samsung.com (KnoxPortal) with ESMTPA id 20250626072102eucas1p1be8a47bb942ca25436f9985c45a01c95~MhrPYoBcn1644116441eucas1p14; Thu, 26 Jun 2025 07:21:02 +0000 (GMT) Received: from [106.210.134.192] (unknown [106.210.134.192]) by eusmtip1.samsung.com (KnoxPortal) with ESMTPA id 20250626072101eusmtip17c426e105c6e0e527e20a4ad58cc97a1~MhrOgUKZ22676026760eusmtip1X; Thu, 26 Jun 2025 07:21:01 +0000 (GMT) Message-ID: <3acea31c-054c-43a8-a6f7-ab4b5b6a7dca@samsung.com> Date: Thu, 26 Jun 2025 09:21:00 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 2/8] docs: dma-api: replace consistent with coherent To: Petr Tesarik , Robin Murphy , Christoph Hellwig Cc: Jonathan Corbet , Andrew Morton , Leon Romanovsky , Keith Busch , Caleb Sander Mateos , Sagi Grimberg , Jens Axboe , John Garry , "open list:DOCUMENTATION" , open list , "open list:MEMORY MANAGEMENT" , iommu@lists.linux.dev Content-Language: en-US From: Marek Szyprowski In-Reply-To: <20250626065123.646bd954@mordecai.tesarici.cz> Content-Transfer-Encoding: 7bit X-CMS-MailID: 20250626072102eucas1p1be8a47bb942ca25436f9985c45a01c95 X-Msg-Generator: CA Content-Type: text/plain; charset="utf-8" X-RootMTR: 20250626045133eucas1p1d5070046a3303f6b2fe7f9ec75d08f02 X-EPHeader: CA X-CMS-RootMailID: 20250626045133eucas1p1d5070046a3303f6b2fe7f9ec75d08f02 References: <20250624133923.1140421-1-ptesarik@suse.com> <20250624133923.1140421-3-ptesarik@suse.com> <20250626065123.646bd954@mordecai.tesarici.cz> X-Rspamd-Queue-Id: B1AA818000C X-Rspam-User: X-Rspamd-Server: rspam06 X-Stat-Signature: gput1cpzxdn385h3ezgw1eikhosy3ieo X-HE-Tag: 1750922464-842004 X-HE-Meta: U2FsdGVkX1+huTc6sCnjGaYvkluFpWFYVlcGk8mYnqYmluGxs/ZM/nDQvOl7CGUHj+bjUJW8O7lWr07KOF1pn/wfoNaJ3076sA2bA5ZVSOutl4r1vumQGShAql5/pgnQ1CVpXWWGPrPG2vWOK0HDQis162/mlOQlV9idOshie+B3Uw4zCk9+WTzZaDFdGp1PEpR8rmwZEC/g5K0NuuBB++IQ2eZuzFpKDeg/0bfyUjZlznc1B+atPoXuhvVHDVYprP2BFNKKH6Z5zlDa6g2l+QWBN2On2WQXonobi3jQZQJ+GQeWxhY2tCfN/+uB8a6DazSlL+vEEiGcCUg5Iz5IsS5pJBYXL3HXROS1Ung0pXiKnvoMCckJqhEFNVTDtTKoQ5TWYfKouGTGWab/ogcR3UKNaGsuR1GBGpWhd+/0waO8Z6BBSo8gXbkojk6epswvpkc/VlJ1OqhVdUEh8kUYzNfvDhXWYwLOBUGFma9JL6sQ6kNQcpM2BRp/RyoFj31oMrKjems/Bhkccc/Ri897al2TfgrIieiwvwvM0mq7rU5CnNCHurpl1YJB6GDHyx/EMXS9sNivNE+5H09iSEeXMa22y5uWDhu475r+F1PDZa/Ux+4TYLauUoFmlft7F2NOT5rcskUdSZFS7yCECkXe/WAY4IWCS+XFYI+cqqPvS82wso9WhBvXE3RLb+zE+BAfcNg8g5LvrxsF1Ak4RI5KcTFHSXQM7QaH3vUL9IdaUxk1eWS6TV2/+MHU7YWP/p+o2Wv3eiEP39ydxF2xUUXeCb5WvSN7OXnDZz5toftzPx5rbuwE0ghSMzoiThGpdu6uwOwtmCKna5ORxA9SPxFYDfsBZ3TtxreLqq0Q/gq4aWsoYYYi2VVLQYwhpARb9mRPIzygZ6UzZtsKnMEwr+Wj84TUl2s7qE3nYVXt8OX1UkcSC5wMxlR7I8+mVcBjII2AP2CMEpt6flUiJtx9w/T dqWUwJgo 2Xz/sWXglKOsGB6ZvgNMc6Dl5nw/vFKON3EriHOYF+9DPoVAPBH7DeDZmOEsILafS4qis3wwpZgvzzBkJPspLNuQWInqRC4t+fD2k X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: On 26.06.2025 06:51, Petr Tesarik wrote: > On Tue, 24 Jun 2025 15:39:17 +0200 > Petr Tesarik wrote: > >> For consistency, always use the term "coherent" when talking about memory >> that is not subject to CPU caching effects. The term "consistent" is a >> relic of a long-removed pci_alloc_consistent() function. > I realize that I'm not an authoritative source for this, but I forgot > to add more trusted maintainers to the recipient list. > > Now, all you DMA experts, do you agree that the word "consistent" > should be finally eradicated from DMA API documentation? Well, this was always puzzling for me, why there are those 2 names used (especially in case of dma_alloc_coherent() vs. dma_alloc_nonconsistent()). I'm for unifying them to "coherent" as this is the term use more often. > > ... Best regards -- Marek Szyprowski, PhD Samsung R&D Institute Poland