[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5e5ee5d3-8a57-478a-9ce7-b40cab60b67d@amd.com>
Date: Wed, 10 Jul 2024 16:14:18 +0200
From: Christian König <christian.koenig@....com>
To: Lei Liu <liulei.rjpt@...o.com>, Sumit Semwal <sumit.semwal@...aro.org>,
Benjamin Gaignard <benjamin.gaignard@...labora.com>,
Brian Starkey <Brian.Starkey@....com>, John Stultz <jstultz@...gle.com>,
"T.J. Mercier" <tjmercier@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
David Hildenbrand <david@...hat.com>, Matthew Wilcox <willy@...radead.org>,
Muhammad Usama Anjum <usama.anjum@...labora.com>,
Andrei Vagin <avagin@...gle.com>, Ryan Roberts <ryan.roberts@....com>,
Kefeng Wang <wangkefeng.wang@...wei.com>, linux-media@...r.kernel.org,
dri-devel@...ts.freedesktop.org, linaro-mm-sig@...ts.linaro.org,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-mm@...ck.org, Daniel Vetter <daniel@...ll.ch>,
"Vetter, Daniel" <daniel.vetter@...el.com>
Cc: opensource.kernel@...o.com
Subject: Re: [PATCH 0/2] Support direct I/O read and write for memory
allocated by dmabuf
Am 10.07.24 um 15:57 schrieb Lei Liu:
> Use vm_insert_page to establish a mapping for the memory allocated
> by dmabuf, thus supporting direct I/O read and write; and fix the
> issue of incorrect memory statistics after mapping dmabuf memory.
Well big NAK to that! Direct I/O is intentionally disabled on DMA-bufs.
We already discussed enforcing that in the DMA-buf framework and this
patch probably means that we should really do that.
Regards,
Christian.
>
> Lei Liu (2):
> mm: dmabuf_direct_io: Support direct_io for memory allocated by dmabuf
> mm: dmabuf_direct_io: Fix memory statistics error for dmabuf allocated
> memory with direct_io support
>
> drivers/dma-buf/heaps/system_heap.c | 5 +++--
> fs/proc/task_mmu.c | 8 +++++++-
> include/linux/mm.h | 1 +
> mm/memory.c | 15 ++++++++++-----
> mm/rmap.c | 9 +++++----
> 5 files changed, 26 insertions(+), 12 deletions(-)
>
Powered by blists - more mailing lists