From: Jason Gunthorpe <jgg@nvidia.com>
To: Lu Baolu <baolu.lu@linux.intel.com>,
Joerg Roedel <joro@8bytes.org>, Kevin Tian <kevin.tian@intel.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Robin Murphy <robin.murphy@arm.com>
Cc: linux-s390@vger.kernel.org, kvm@vger.kernel.org,
nouveau@lists.freedesktop.org, linux-rdma@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Niklas Schnelle <schnelle@linux.ibm.com>,
linux-remoteproc@vger.kernel.org, iommu@lists.linux.dev,
dri-devel@lists.freedesktop.org,
linux-stm32@st-md-mailman.stormreply.com,
Alex Williamson <alex.williamson@redhat.com>,
netdev@vger.kernel.org, ath10k@lists.infradead.org,
linux-wireless@vger.kernel.org, linux-tegra@vger.kernel.org,
Christian Borntraeger <borntraeger@linux.ibm.com>,
virtualization@lists.linux-foundation.org,
ath11k@lists.infradead.org, linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: [Nouveau] [PATCH 5/8] iommufd: Use GFP_KERNEL_ACCOUNT for iommu_map()
Date: Fri, 6 Jan 2023 12:42:45 -0400 [thread overview]
Message-ID: <5-v1-6e8b3997c46d+89e-iommu_map_gfp_jgg@nvidia.com> (raw)
In-Reply-To: <0-v1-6e8b3997c46d+89e-iommu_map_gfp_jgg@nvidia.com>
iommufd follows the same design as KVM and uses memory cgroups to limit
the amount of kernel memory a iommufd file descriptor can pin down. The
various internal data structures already use GFP_KERNEL_ACCOUNT.
However, one of the biggest consumers of kernel memory is the IOPTEs
stored under the iommu_domain. Many drivers will allocate these at
iommu_map() time and will trivially do the right thing if we pass in
GFP_KERNEL_ACCOUNT.
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
---
drivers/iommu/iommufd/pages.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/iommu/iommufd/pages.c b/drivers/iommu/iommufd/pages.c
index 22cc3bb0c6c55a..f8d92c9bb65b60 100644
--- a/drivers/iommu/iommufd/pages.c
+++ b/drivers/iommu/iommufd/pages.c
@@ -457,7 +457,7 @@ static int batch_iommu_map_small(struct iommu_domain *domain,
while (size) {
rc = iommu_map(domain, iova, paddr, PAGE_SIZE, prot,
- GFP_KERNEL);
+ GFP_KERNEL_ACCOUNT);
if (rc)
goto err_unmap;
iova += PAGE_SIZE;
@@ -502,7 +502,7 @@ static int batch_to_domain(struct pfn_batch *batch, struct iommu_domain *domain,
rc = iommu_map(domain, iova,
PFN_PHYS(batch->pfns[cur]) + page_offset,
next_iova - iova, area->iommu_prot,
- GFP_KERNEL);
+ GFP_KERNEL_ACCOUNT);
if (rc)
goto err_unmap;
iova = next_iova;
--
2.39.0
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Lu Baolu <baolu.lu@linux.intel.com>,
Joerg Roedel <joro@8bytes.org>, Kevin Tian <kevin.tian@intel.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Robin Murphy <robin.murphy@arm.com>
Cc: linux-s390@vger.kernel.org, kvm@vger.kernel.org,
nouveau@lists.freedesktop.org, linux-rdma@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Niklas Schnelle <schnelle@linux.ibm.com>,
linux-remoteproc@vger.kernel.org, iommu@lists.linux.dev,
dri-devel@lists.freedesktop.org,
linux-stm32@st-md-mailman.stormreply.com,
Alex Williamson <alex.williamson@redhat.com>,
netdev@vger.kernel.org, ath10k@lists.infradead.org,
linux-wireless@vger.kernel.org, linux-tegra@vger.kernel.org,
Christian Borntraeger <borntraeger@linux.ibm.com>,
virtualization@lists.linux-foundation.org,
ath11k@lists.infradead.org, linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: [PATCH 5/8] iommufd: Use GFP_KERNEL_ACCOUNT for iommu_map()
Date: Fri, 6 Jan 2023 12:42:45 -0400 [thread overview]
Message-ID: <5-v1-6e8b3997c46d+89e-iommu_map_gfp_jgg@nvidia.com> (raw)
In-Reply-To: <0-v1-6e8b3997c46d+89e-iommu_map_gfp_jgg@nvidia.com>
iommufd follows the same design as KVM and uses memory cgroups to limit
the amount of kernel memory a iommufd file descriptor can pin down. The
various internal data structures already use GFP_KERNEL_ACCOUNT.
However, one of the biggest consumers of kernel memory is the IOPTEs
stored under the iommu_domain. Many drivers will allocate these at
iommu_map() time and will trivially do the right thing if we pass in
GFP_KERNEL_ACCOUNT.
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
---
drivers/iommu/iommufd/pages.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/iommu/iommufd/pages.c b/drivers/iommu/iommufd/pages.c
index 22cc3bb0c6c55a..f8d92c9bb65b60 100644
--- a/drivers/iommu/iommufd/pages.c
+++ b/drivers/iommu/iommufd/pages.c
@@ -457,7 +457,7 @@ static int batch_iommu_map_small(struct iommu_domain *domain,
while (size) {
rc = iommu_map(domain, iova, paddr, PAGE_SIZE, prot,
- GFP_KERNEL);
+ GFP_KERNEL_ACCOUNT);
if (rc)
goto err_unmap;
iova += PAGE_SIZE;
@@ -502,7 +502,7 @@ static int batch_to_domain(struct pfn_batch *batch, struct iommu_domain *domain,
rc = iommu_map(domain, iova,
PFN_PHYS(batch->pfns[cur]) + page_offset,
next_iova - iova, area->iommu_prot,
- GFP_KERNEL);
+ GFP_KERNEL_ACCOUNT);
if (rc)
goto err_unmap;
iova = next_iova;
--
2.39.0
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Lu Baolu <baolu.lu@linux.intel.com>,
Joerg Roedel <joro@8bytes.org>, Kevin Tian <kevin.tian@intel.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Robin Murphy <robin.murphy@arm.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
ath10k@lists.infradead.org, ath11k@lists.infradead.org,
Christian Borntraeger <borntraeger@linux.ibm.com>,
dri-devel@lists.freedesktop.org, iommu@lists.linux.dev,
kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-media@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-remoteproc@vger.kernel.org,
linux-s390@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-tegra@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, nouveau@lists.freedesktop.org,
Niklas Schnelle <schnelle@linux.ibm.com>,
virtualization@lists.linux-foundation.org
Subject: [PATCH 5/8] iommufd: Use GFP_KERNEL_ACCOUNT for iommu_map()
Date: Fri, 6 Jan 2023 12:42:45 -0400 [thread overview]
Message-ID: <5-v1-6e8b3997c46d+89e-iommu_map_gfp_jgg@nvidia.com> (raw)
In-Reply-To: <0-v1-6e8b3997c46d+89e-iommu_map_gfp_jgg@nvidia.com>
iommufd follows the same design as KVM and uses memory cgroups to limit
the amount of kernel memory a iommufd file descriptor can pin down. The
various internal data structures already use GFP_KERNEL_ACCOUNT.
However, one of the biggest consumers of kernel memory is the IOPTEs
stored under the iommu_domain. Many drivers will allocate these at
iommu_map() time and will trivially do the right thing if we pass in
GFP_KERNEL_ACCOUNT.
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
---
drivers/iommu/iommufd/pages.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/iommu/iommufd/pages.c b/drivers/iommu/iommufd/pages.c
index 22cc3bb0c6c55a..f8d92c9bb65b60 100644
--- a/drivers/iommu/iommufd/pages.c
+++ b/drivers/iommu/iommufd/pages.c
@@ -457,7 +457,7 @@ static int batch_iommu_map_small(struct iommu_domain *domain,
while (size) {
rc = iommu_map(domain, iova, paddr, PAGE_SIZE, prot,
- GFP_KERNEL);
+ GFP_KERNEL_ACCOUNT);
if (rc)
goto err_unmap;
iova += PAGE_SIZE;
@@ -502,7 +502,7 @@ static int batch_to_domain(struct pfn_batch *batch, struct iommu_domain *domain,
rc = iommu_map(domain, iova,
PFN_PHYS(batch->pfns[cur]) + page_offset,
next_iova - iova, area->iommu_prot,
- GFP_KERNEL);
+ GFP_KERNEL_ACCOUNT);
if (rc)
goto err_unmap;
iova = next_iova;
--
2.39.0
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Lu Baolu <baolu.lu@linux.intel.com>,
Joerg Roedel <joro@8bytes.org>, Kevin Tian <kevin.tian@intel.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Robin Murphy <robin.murphy@arm.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
ath10k@lists.infradead.org, ath11k@lists.infradead.org,
Christian Borntraeger <borntraeger@linux.ibm.com>,
dri-devel@lists.freedesktop.org, iommu@lists.linux.dev,
kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-media@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-remoteproc@vger.kernel.org,
linux-s390@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-tegra@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, nouveau@lists.freedesktop.org,
Niklas Schnelle <schnelle@linux.ibm.com>,
virtualization@lists.linux-foundation.org
Subject: [PATCH 5/8] iommufd: Use GFP_KERNEL_ACCOUNT for iommu_map()
Date: Fri, 6 Jan 2023 12:42:45 -0400 [thread overview]
Message-ID: <5-v1-6e8b3997c46d+89e-iommu_map_gfp_jgg@nvidia.com> (raw)
In-Reply-To: <0-v1-6e8b3997c46d+89e-iommu_map_gfp_jgg@nvidia.com>
iommufd follows the same design as KVM and uses memory cgroups to limit
the amount of kernel memory a iommufd file descriptor can pin down. The
various internal data structures already use GFP_KERNEL_ACCOUNT.
However, one of the biggest consumers of kernel memory is the IOPTEs
stored under the iommu_domain. Many drivers will allocate these at
iommu_map() time and will trivially do the right thing if we pass in
GFP_KERNEL_ACCOUNT.
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
---
drivers/iommu/iommufd/pages.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/iommu/iommufd/pages.c b/drivers/iommu/iommufd/pages.c
index 22cc3bb0c6c55a..f8d92c9bb65b60 100644
--- a/drivers/iommu/iommufd/pages.c
+++ b/drivers/iommu/iommufd/pages.c
@@ -457,7 +457,7 @@ static int batch_iommu_map_small(struct iommu_domain *domain,
while (size) {
rc = iommu_map(domain, iova, paddr, PAGE_SIZE, prot,
- GFP_KERNEL);
+ GFP_KERNEL_ACCOUNT);
if (rc)
goto err_unmap;
iova += PAGE_SIZE;
@@ -502,7 +502,7 @@ static int batch_to_domain(struct pfn_batch *batch, struct iommu_domain *domain,
rc = iommu_map(domain, iova,
PFN_PHYS(batch->pfns[cur]) + page_offset,
next_iova - iova, area->iommu_prot,
- GFP_KERNEL);
+ GFP_KERNEL_ACCOUNT);
if (rc)
goto err_unmap;
iova = next_iova;
--
2.39.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Lu Baolu <baolu.lu@linux.intel.com>,
Joerg Roedel <joro@8bytes.org>, Kevin Tian <kevin.tian@intel.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Robin Murphy <robin.murphy@arm.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
ath10k@lists.infradead.org, ath11k@lists.infradead.org,
Christian Borntraeger <borntraeger@linux.ibm.com>,
dri-devel@lists.freedesktop.org, iommu@lists.linux.dev,
kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-media@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-remoteproc@vger.kernel.org,
linux-s390@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-tegra@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, nouveau@lists.freedesktop.org,
Niklas Schnelle <schnelle@linux.ibm.com>,
virtualization@lists.linux-foundation.org
Subject: [PATCH 5/8] iommufd: Use GFP_KERNEL_ACCOUNT for iommu_map()
Date: Fri, 6 Jan 2023 12:42:45 -0400 [thread overview]
Message-ID: <5-v1-6e8b3997c46d+89e-iommu_map_gfp_jgg@nvidia.com> (raw)
In-Reply-To: <0-v1-6e8b3997c46d+89e-iommu_map_gfp_jgg@nvidia.com>
iommufd follows the same design as KVM and uses memory cgroups to limit
the amount of kernel memory a iommufd file descriptor can pin down. The
various internal data structures already use GFP_KERNEL_ACCOUNT.
However, one of the biggest consumers of kernel memory is the IOPTEs
stored under the iommu_domain. Many drivers will allocate these at
iommu_map() time and will trivially do the right thing if we pass in
GFP_KERNEL_ACCOUNT.
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
---
drivers/iommu/iommufd/pages.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/iommu/iommufd/pages.c b/drivers/iommu/iommufd/pages.c
index 22cc3bb0c6c55a..f8d92c9bb65b60 100644
--- a/drivers/iommu/iommufd/pages.c
+++ b/drivers/iommu/iommufd/pages.c
@@ -457,7 +457,7 @@ static int batch_iommu_map_small(struct iommu_domain *domain,
while (size) {
rc = iommu_map(domain, iova, paddr, PAGE_SIZE, prot,
- GFP_KERNEL);
+ GFP_KERNEL_ACCOUNT);
if (rc)
goto err_unmap;
iova += PAGE_SIZE;
@@ -502,7 +502,7 @@ static int batch_to_domain(struct pfn_batch *batch, struct iommu_domain *domain,
rc = iommu_map(domain, iova,
PFN_PHYS(batch->pfns[cur]) + page_offset,
next_iova - iova, area->iommu_prot,
- GFP_KERNEL);
+ GFP_KERNEL_ACCOUNT);
if (rc)
goto err_unmap;
iova = next_iova;
--
2.39.0
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Lu Baolu <baolu.lu@linux.intel.com>,
Joerg Roedel <joro@8bytes.org>, Kevin Tian <kevin.tian@intel.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Robin Murphy <robin.murphy@arm.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
ath10k@lists.infradead.org, ath11k@lists.infradead.org,
Christian Borntraeger <borntraeger@linux.ibm.com>,
dri-devel@lists.freedesktop.org, iommu@lists.linux.dev,
kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-media@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-remoteproc@vger.kernel.org,
linux-s390@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-tegra@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, nouveau@lists.freedesktop.org,
Niklas Schnelle <schnelle@linux.ibm.com>,
virtualization@lists.linux-foundation.org
Subject: [PATCH 5/8] iommufd: Use GFP_KERNEL_ACCOUNT for iommu_map()
Date: Fri, 6 Jan 2023 12:42:45 -0400 [thread overview]
Message-ID: <5-v1-6e8b3997c46d+89e-iommu_map_gfp_jgg@nvidia.com> (raw)
In-Reply-To: <0-v1-6e8b3997c46d+89e-iommu_map_gfp_jgg@nvidia.com>
iommufd follows the same design as KVM and uses memory cgroups to limit
the amount of kernel memory a iommufd file descriptor can pin down. The
various internal data structures already use GFP_KERNEL_ACCOUNT.
However, one of the biggest consumers of kernel memory is the IOPTEs
stored under the iommu_domain. Many drivers will allocate these at
iommu_map() time and will trivially do the right thing if we pass in
GFP_KERNEL_ACCOUNT.
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
---
drivers/iommu/iommufd/pages.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/iommu/iommufd/pages.c b/drivers/iommu/iommufd/pages.c
index 22cc3bb0c6c55a..f8d92c9bb65b60 100644
--- a/drivers/iommu/iommufd/pages.c
+++ b/drivers/iommu/iommufd/pages.c
@@ -457,7 +457,7 @@ static int batch_iommu_map_small(struct iommu_domain *domain,
while (size) {
rc = iommu_map(domain, iova, paddr, PAGE_SIZE, prot,
- GFP_KERNEL);
+ GFP_KERNEL_ACCOUNT);
if (rc)
goto err_unmap;
iova += PAGE_SIZE;
@@ -502,7 +502,7 @@ static int batch_to_domain(struct pfn_batch *batch, struct iommu_domain *domain,
rc = iommu_map(domain, iova,
PFN_PHYS(batch->pfns[cur]) + page_offset,
next_iova - iova, area->iommu_prot,
- GFP_KERNEL);
+ GFP_KERNEL_ACCOUNT);
if (rc)
goto err_unmap;
iova = next_iova;
--
2.39.0
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2023-01-06 16:42 UTC|newest]
Thread overview: 144+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 16:42 [Nouveau] [PATCH 0/8] Let iommufd charge IOPTE allocations to the memory cgroup Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` [Nouveau] [PATCH 1/8] iommu: Add a gfp parameter to iommu_map() Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 17:15 ` Robin Murphy
2023-01-06 17:15 ` Robin Murphy
2023-01-06 17:15 ` Robin Murphy
2023-01-06 17:15 ` Robin Murphy
2023-01-06 17:15 ` Robin Murphy
2023-01-06 17:15 ` Robin Murphy
2023-01-06 17:15 ` [Nouveau] " Robin Murphy
2023-01-06 17:24 ` Jason Gunthorpe
2023-01-06 17:24 ` Jason Gunthorpe
2023-01-06 17:24 ` Jason Gunthorpe
2023-01-06 17:24 ` Jason Gunthorpe
2023-01-06 17:24 ` Jason Gunthorpe
2023-01-06 17:24 ` Jason Gunthorpe
2023-01-20 9:24 ` Joerg Roedel
2023-01-20 9:24 ` Joerg Roedel
2023-01-20 9:24 ` Joerg Roedel
2023-01-20 9:24 ` Joerg Roedel
2023-01-20 9:24 ` Joerg Roedel
2023-01-20 9:24 ` Joerg Roedel
2023-01-20 9:24 ` [Nouveau] " Joerg Roedel
2023-01-20 17:53 ` Jason Gunthorpe
2023-01-20 17:53 ` Jason Gunthorpe
2023-01-20 17:53 ` Jason Gunthorpe
2023-01-20 17:53 ` Jason Gunthorpe
2023-01-20 17:53 ` Jason Gunthorpe
2023-01-20 17:53 ` [Nouveau] " Jason Gunthorpe
2023-01-23 9:59 ` Joerg Roedel
2023-01-23 9:59 ` Joerg Roedel
2023-01-23 9:59 ` Joerg Roedel
2023-01-23 9:59 ` Joerg Roedel
2023-01-23 9:59 ` Joerg Roedel
2023-01-23 9:59 ` Joerg Roedel
2023-01-23 9:59 ` Joerg Roedel
2023-01-16 18:12 ` [Nouveau] " Jason Gunthorpe
2023-01-16 18:12 ` Jason Gunthorpe
2023-01-16 18:12 ` Jason Gunthorpe
2023-01-16 18:12 ` Jason Gunthorpe
2023-01-16 18:12 ` Jason Gunthorpe
2023-01-16 18:12 ` Jason Gunthorpe
2023-01-06 16:42 ` [Nouveau] [PATCH 2/8] iommu: Remove iommu_map_atomic() Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` [Nouveau] [PATCH 3/8] iommu: Add a gfp parameter to iommu_map_sg() Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` [Nouveau] [PATCH 4/8] iommu/dma: Use the gfp parameter in __iommu_dma_alloc_noncontiguous() Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe [this message]
2023-01-06 16:42 ` [PATCH 5/8] iommufd: Use GFP_KERNEL_ACCOUNT for iommu_map() Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` [Nouveau] [PATCH 6/8] iommu/intel: Add a gfp parameter to alloc_pgtable_page() Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-17 3:35 ` Tian, Kevin
2023-01-17 3:35 ` [Nouveau] " Tian, Kevin
2023-01-17 3:35 ` Tian, Kevin
2023-01-17 3:35 ` Tian, Kevin
2023-01-17 3:35 ` Tian, Kevin
2023-01-17 3:35 ` Tian, Kevin
2023-01-17 3:35 ` Tian, Kevin
2023-01-17 13:30 ` Jason Gunthorpe
2023-01-17 13:30 ` Jason Gunthorpe
2023-01-17 13:30 ` Jason Gunthorpe
2023-01-17 13:30 ` Jason Gunthorpe
2023-01-17 13:30 ` Jason Gunthorpe
2023-01-17 13:30 ` [Nouveau] " Jason Gunthorpe
2023-01-18 1:18 ` Tian, Kevin
2023-01-18 1:18 ` [Nouveau] " Tian, Kevin
2023-01-18 1:18 ` Tian, Kevin
2023-01-18 1:18 ` Tian, Kevin
2023-01-18 1:18 ` Tian, Kevin
2023-01-18 1:18 ` Tian, Kevin
2023-01-18 1:18 ` Tian, Kevin
2023-01-18 15:15 ` [Nouveau] " Jason Gunthorpe
2023-01-18 15:15 ` Jason Gunthorpe
2023-01-18 15:15 ` Jason Gunthorpe
2023-01-18 15:15 ` Jason Gunthorpe
2023-01-18 15:15 ` Jason Gunthorpe
2023-01-18 15:15 ` Jason Gunthorpe
2023-01-06 16:42 ` [Nouveau] [PATCH 7/8] iommu/intel: Support the gfp argument to the map_pages op Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-17 3:38 ` Tian, Kevin
2023-01-17 3:38 ` [Nouveau] " Tian, Kevin
2023-01-17 3:38 ` Tian, Kevin
2023-01-17 3:38 ` Tian, Kevin
2023-01-17 3:38 ` Tian, Kevin
2023-01-17 3:38 ` Tian, Kevin
2023-01-17 3:38 ` Tian, Kevin
2023-01-17 8:35 ` Baolu Lu
2023-01-17 8:35 ` [Nouveau] " Baolu Lu
2023-01-17 8:35 ` Baolu Lu
2023-01-17 8:35 ` Baolu Lu
2023-01-17 8:35 ` Baolu Lu
2023-01-17 8:35 ` Baolu Lu
2023-01-17 13:28 ` Jason Gunthorpe
2023-01-17 13:28 ` Jason Gunthorpe
2023-01-17 13:28 ` Jason Gunthorpe
2023-01-17 13:28 ` Jason Gunthorpe
2023-01-17 13:28 ` Jason Gunthorpe
2023-01-17 13:28 ` [Nouveau] " Jason Gunthorpe
2023-01-06 16:42 ` [Nouveau] [PATCH 8/8] iommu/s390: Push the gfp parameter to the kmem_cache_alloc()'s Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-17 8:49 ` Niklas Schnelle
2023-01-17 8:49 ` [Nouveau] " Niklas Schnelle
2023-01-17 8:49 ` Niklas Schnelle
2023-01-17 8:49 ` Niklas Schnelle
2023-01-17 8:49 ` Niklas Schnelle
2023-01-17 8:49 ` Niklas Schnelle
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=5-v1-6e8b3997c46d+89e-iommu_map_gfp_jgg@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=ath10k@lists.infradead.org \
--cc=ath11k@lists.infradead.org \
--cc=baolu.lu@linux.intel.com \
--cc=borntraeger@linux.ibm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=robin.murphy@arm.com \
--cc=schnelle@linux.ibm.com \
--cc=virtualization@lists.linux-foundation.org \
/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 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.