From: David Rientjes <rientjes@google.com> To: Christoph Hellwig <hch@lst.de>, Tom Lendacky <thomas.lendacky@amd.com> Cc: "Singh, Brijesh" <brijesh.singh@amd.com>, "Grimm, Jon" <jon.grimm@amd.com>, Joerg Roedel <joro@8bytes.org>, baekhw@google.com, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "iommu@lists.linux-foundation.org" <iommu@lists.linux-foundation.org> Subject: [rfc 0/6] unencrypted atomic DMA pools with dynamic expansion Date: Sun, 1 Mar 2020 16:05:03 -0800 (PST) [thread overview] Message-ID: <alpine.DEB.2.21.2003011535510.213582@chino.kir.corp.google.com> (raw) In-Reply-To: <alpine.DEB.2.21.2002280118461.165532@chino.kir.corp.google.com> set_memory_decrypted() may block so it is not possible to do non-blocking allocations through the DMA API for devices that required unencrypted memory. The solution is to expand the atomic DMA pools for the various possible gfp requirements as a means to prevent an unnecessary depletion of lowmem. These atomic DMA pools are kept unencrypted so they can immediately be used for non-blocking allocations. Since the need for this type of memory depends on the kernel config and devices being used, these pools are also dynamically expandable. Some of these patches could be squashed into each other, but they were separated out to ease code review. This patchset is based on 5.6-rc4. --- arch/x86/Kconfig | 1 + drivers/iommu/dma-iommu.c | 5 +- include/linux/dma-direct.h | 2 + include/linux/dma-mapping.h | 6 +- kernel/dma/direct.c | 17 ++-- kernel/dma/remap.c | 173 +++++++++++++++++++++++++----------- 6 files changed, 140 insertions(+), 64 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: David Rientjes via iommu <iommu@lists.linux-foundation.org> To: Christoph Hellwig <hch@lst.de>, Tom Lendacky <thomas.lendacky@amd.com> Cc: "Singh, Brijesh" <brijesh.singh@amd.com>, "Grimm, Jon" <jon.grimm@amd.com>, baekhw@google.com, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "iommu@lists.linux-foundation.org" <iommu@lists.linux-foundation.org> Subject: [rfc 0/6] unencrypted atomic DMA pools with dynamic expansion Date: Sun, 1 Mar 2020 16:05:03 -0800 (PST) [thread overview] Message-ID: <alpine.DEB.2.21.2003011535510.213582@chino.kir.corp.google.com> (raw) In-Reply-To: <alpine.DEB.2.21.2002280118461.165532@chino.kir.corp.google.com> set_memory_decrypted() may block so it is not possible to do non-blocking allocations through the DMA API for devices that required unencrypted memory. The solution is to expand the atomic DMA pools for the various possible gfp requirements as a means to prevent an unnecessary depletion of lowmem. These atomic DMA pools are kept unencrypted so they can immediately be used for non-blocking allocations. Since the need for this type of memory depends on the kernel config and devices being used, these pools are also dynamically expandable. Some of these patches could be squashed into each other, but they were separated out to ease code review. This patchset is based on 5.6-rc4. --- arch/x86/Kconfig | 1 + drivers/iommu/dma-iommu.c | 5 +- include/linux/dma-direct.h | 2 + include/linux/dma-mapping.h | 6 +- kernel/dma/direct.c | 17 ++-- kernel/dma/remap.c | 173 +++++++++++++++++++++++++----------- 6 files changed, 140 insertions(+), 64 deletions(-) _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-03-02 0:05 UTC|newest] Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-01-01 1:54 [rfc] dma-mapping: preallocate unencrypted DMA atomic pool David Rientjes 2020-01-01 1:54 ` David Rientjes via iommu 2020-01-06 17:34 ` Robin Murphy 2020-01-06 17:34 ` Robin Murphy 2020-01-07 10:54 ` Christoph Hellwig 2020-01-07 10:54 ` Christoph Hellwig 2020-01-07 19:57 ` David Rientjes 2020-01-07 19:57 ` David Rientjes via iommu 2020-01-09 14:31 ` Christoph Hellwig 2020-01-09 14:31 ` Christoph Hellwig 2020-01-09 18:58 ` David Rientjes 2020-01-09 18:58 ` David Rientjes via iommu 2020-01-17 15:28 ` Tom Lendacky 2020-01-17 15:28 ` Tom Lendacky 2020-02-28 9:27 ` David Rientjes 2020-02-28 9:27 ` David Rientjes via iommu 2020-03-02 0:05 ` David Rientjes [this message] 2020-03-02 0:05 ` [rfc 0/6] unencrypted atomic DMA pools with dynamic expansion David Rientjes via iommu 2020-03-02 0:05 ` [rfc 1/6] dma-mapping: pass device to atomic allocation functions David Rientjes 2020-03-02 0:05 ` David Rientjes via iommu 2020-03-02 0:05 ` [rfc 2/6] dma-remap: add additional atomic pools to map to gfp mask David Rientjes 2020-03-02 0:05 ` David Rientjes via iommu 2020-03-05 15:42 ` Christoph Hellwig 2020-03-05 15:42 ` Christoph Hellwig 2020-03-02 0:05 ` [rfc 3/6] dma-remap: wire up the atomic pools depending on " David Rientjes 2020-03-02 0:05 ` David Rientjes via iommu 2020-03-05 15:43 ` Christoph Hellwig 2020-03-05 15:43 ` Christoph Hellwig 2020-03-02 0:05 ` [rfc 4/6] dma-remap: dynamically expanding atomic pools David Rientjes 2020-03-02 0:05 ` David Rientjes via iommu 2020-03-03 22:29 ` David Rientjes 2020-03-03 22:29 ` David Rientjes via iommu 2020-03-02 0:05 ` [rfc 5/6] dma-direct: atomic allocations must come from unencrypted pools David Rientjes 2020-03-02 0:05 ` David Rientjes via iommu 2020-03-05 15:44 ` Christoph Hellwig 2020-03-05 15:44 ` Christoph Hellwig 2020-03-07 0:36 ` David Rientjes 2020-03-07 0:36 ` David Rientjes via iommu 2020-03-10 18:47 ` Christoph Hellwig 2020-03-10 18:47 ` Christoph Hellwig 2020-03-02 0:05 ` [rfc 6/6] dma-remap: double the default DMA coherent pool size David Rientjes 2020-03-02 0:05 ` David Rientjes via iommu 2020-03-05 15:45 ` Christoph Hellwig 2020-03-05 15:45 ` Christoph Hellwig 2020-04-08 21:21 ` [rfc v2 0/6] unencrypted atomic DMA pools with dynamic expansion David Rientjes 2020-04-08 21:21 ` David Rientjes via iommu 2020-04-08 21:21 ` [rfc v2 1/6] dma-remap: separate DMA atomic pools from direct remap code David Rientjes 2020-04-08 21:21 ` David Rientjes via iommu 2020-04-14 6:35 ` Christoph Hellwig 2020-04-14 6:35 ` Christoph Hellwig 2020-04-08 21:21 ` [rfc v2 2/6] dma-pool: add additional coherent pools to map to gfp mask David Rientjes 2020-04-08 21:21 ` David Rientjes via iommu 2020-04-08 21:21 ` [rfc v2 3/6] dma-pool: dynamically expanding atomic pools David Rientjes 2020-04-08 21:21 ` David Rientjes via iommu 2020-04-08 21:21 ` [rfc v2 4/6] dma-direct: atomic allocations must come from atomic coherent pools David Rientjes 2020-04-08 21:21 ` David Rientjes via iommu 2020-04-09 21:24 ` Tom Lendacky 2020-04-09 21:24 ` Tom Lendacky 2020-04-14 19:18 ` David Rientjes 2020-04-14 19:18 ` David Rientjes via iommu 2020-04-14 6:43 ` Christoph Hellwig 2020-04-14 6:43 ` Christoph Hellwig 2020-04-14 19:20 ` David Rientjes 2020-04-14 19:20 ` David Rientjes via iommu 2020-04-08 21:21 ` [rfc v2 5/6] x86/mm: unencrypted non-blocking DMA allocations use " David Rientjes 2020-04-08 21:21 ` David Rientjes via iommu 2020-04-08 21:21 ` [rfc v2 6/6] dma-pool: scale the default DMA coherent pool size with memory capacity David Rientjes 2020-04-08 21:21 ` David Rientjes via iommu 2020-04-10 14:55 ` [rfc v2 3/6] dma-pool: dynamically expanding atomic pools Hillf Danton 2020-04-10 19:37 ` David Rientjes 2020-04-10 19:37 ` David Rientjes via iommu 2020-04-14 6:44 ` Christoph Hellwig 2020-04-14 6:44 ` Christoph Hellwig 2020-04-14 19:23 ` David Rientjes 2020-04-14 19:23 ` David Rientjes via iommu
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=alpine.DEB.2.21.2003011535510.213582@chino.kir.corp.google.com \ --to=rientjes@google.com \ --cc=baekhw@google.com \ --cc=brijesh.singh@amd.com \ --cc=hch@lst.de \ --cc=iommu@lists.linux-foundation.org \ --cc=jon.grimm@amd.com \ --cc=joro@8bytes.org \ --cc=linux-kernel@vger.kernel.org \ --cc=thomas.lendacky@amd.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.