All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolin Chen <nicolinc@nvidia.com>
To: <will@kernel.org>, <robin.murphy@arm.com>, <jgg@nvidia.com>
Cc: <joro@8bytes.org>, <jean-philippe@linaro.org>,
	<apopple@nvidia.com>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>
Subject: [PATCH 0/3] iommu/arm-smmu-v3: Reduce latency in __arm_smmu_tlb_inv_range()
Date: Tue, 22 Aug 2023 01:45:50 -0700	[thread overview]
Message-ID: <cover.1692693557.git.nicolinc@nvidia.com> (raw)

This series is reformatted from the tlb_invalidate_threshold patch:
https://lore.kernel.org/linux-iommu/ZN5oojF6vKOKB%2FeI@Asurada-Nvidia/
The discussion in the thread above moved towards the direction of adding
an arbitrary max_tlbi_ops (similar to MAX_TLBI_OPS in tlbflush.h file).

The changes here aim to reduce the latency in __arm_smmu_tlb_inv_range()
due to the large number of TLBI commands on an SMMU without the support
of range TLBI commands. The solution is to add a threshold at the number
of TLBI commands that one __arm_smmu_tlb_inv_range() callback can issue,
and to replace those TLBI commands with one single per-asid or per-vmid
TLBI command.

Nicolin Chen (3):
  iommu/io-pgtable-arm: Add nents_per_pgtable in struct io_pgtable_cfg
  iommu/arm-smmu-v3: Add an arm_smmu_tlb_inv_domain helper
  iommu/arm-smmu-v3: Add a max_tlbi_ops for __arm_smmu_tlb_inv_range()

 drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 34 +++++++++++++++------
 drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h |  1 +
 drivers/iommu/io-pgtable-arm.c              |  3 ++
 include/linux/io-pgtable.h                  |  2 ++
 4 files changed, 30 insertions(+), 10 deletions(-)

-- 
2.41.0


WARNING: multiple messages have this Message-ID (diff)
From: Nicolin Chen <nicolinc@nvidia.com>
To: <will@kernel.org>, <robin.murphy@arm.com>, <jgg@nvidia.com>
Cc: <joro@8bytes.org>, <jean-philippe@linaro.org>,
	<apopple@nvidia.com>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>
Subject: [PATCH 0/3] iommu/arm-smmu-v3: Reduce latency in __arm_smmu_tlb_inv_range()
Date: Tue, 22 Aug 2023 01:45:50 -0700	[thread overview]
Message-ID: <cover.1692693557.git.nicolinc@nvidia.com> (raw)

This series is reformatted from the tlb_invalidate_threshold patch:
https://lore.kernel.org/linux-iommu/ZN5oojF6vKOKB%2FeI@Asurada-Nvidia/
The discussion in the thread above moved towards the direction of adding
an arbitrary max_tlbi_ops (similar to MAX_TLBI_OPS in tlbflush.h file).

The changes here aim to reduce the latency in __arm_smmu_tlb_inv_range()
due to the large number of TLBI commands on an SMMU without the support
of range TLBI commands. The solution is to add a threshold at the number
of TLBI commands that one __arm_smmu_tlb_inv_range() callback can issue,
and to replace those TLBI commands with one single per-asid or per-vmid
TLBI command.

Nicolin Chen (3):
  iommu/io-pgtable-arm: Add nents_per_pgtable in struct io_pgtable_cfg
  iommu/arm-smmu-v3: Add an arm_smmu_tlb_inv_domain helper
  iommu/arm-smmu-v3: Add a max_tlbi_ops for __arm_smmu_tlb_inv_range()

 drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 34 +++++++++++++++------
 drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h |  1 +
 drivers/iommu/io-pgtable-arm.c              |  3 ++
 include/linux/io-pgtable.h                  |  2 ++
 4 files changed, 30 insertions(+), 10 deletions(-)

-- 
2.41.0


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2023-08-22  8:46 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22  8:45 Nicolin Chen [this message]
2023-08-22  8:45 ` [PATCH 0/3] iommu/arm-smmu-v3: Reduce latency in __arm_smmu_tlb_inv_range() Nicolin Chen
2023-08-22  8:45 ` [PATCH 1/3] iommu/io-pgtable-arm: Add nents_per_pgtable in struct io_pgtable_cfg Nicolin Chen
2023-08-22  8:45   ` Nicolin Chen
2023-08-22  9:19   ` Robin Murphy
2023-08-22  9:19     ` Robin Murphy
2023-08-22 16:42     ` Nicolin Chen
2023-08-22 16:42       ` Nicolin Chen
2023-08-29 15:37       ` Robin Murphy
2023-08-29 15:37         ` Robin Murphy
2023-08-29 20:15         ` Nicolin Chen
2023-08-29 20:15           ` Nicolin Chen
2023-08-29 21:25           ` Robin Murphy
2023-08-29 21:25             ` Robin Murphy
2023-08-29 22:15             ` Nicolin Chen
2023-08-29 22:15               ` Nicolin Chen
2023-08-30 21:49               ` Will Deacon
2023-08-30 21:49                 ` Will Deacon
2023-08-31 17:39                 ` Nicolin Chen
2023-08-31 17:39                   ` Nicolin Chen
2023-09-01  0:08                   ` Nicolin Chen
2023-09-01  0:08                     ` Nicolin Chen
2023-09-01 18:02                     ` Robin Murphy
2023-09-01 18:02                       ` Robin Murphy
2023-09-01 18:23                       ` Nicolin Chen
2023-09-01 18:23                         ` Nicolin Chen
2024-01-20 19:59             ` Nicolin Chen
2024-01-20 19:59               ` Nicolin Chen
2024-01-22 13:01               ` Jason Gunthorpe
2024-01-22 13:01                 ` Jason Gunthorpe
2024-01-22 17:24                 ` Nicolin Chen
2024-01-22 17:24                   ` Nicolin Chen
2024-01-22 17:57                   ` Jason Gunthorpe
2024-01-22 17:57                     ` Jason Gunthorpe
2024-01-24  0:11                     ` Nicolin Chen
2024-01-24  0:11                       ` Nicolin Chen
2024-01-25 13:55                       ` Jason Gunthorpe
2024-01-25 13:55                         ` Jason Gunthorpe
2024-01-25 17:23                         ` Nicolin Chen
2024-01-25 17:23                           ` Nicolin Chen
2024-01-25 17:47                           ` Jason Gunthorpe
2024-01-25 17:47                             ` Jason Gunthorpe
2024-01-25 19:55                             ` Nicolin Chen
2024-01-25 19:55                               ` Nicolin Chen
     [not found]                   ` <098d64da-ecf5-4a23-bff9-a04840726ef0@huawei.com>
2024-01-25  5:09                     ` Nicolin Chen
2024-01-25  5:09                       ` Nicolin Chen
2023-08-22  8:45 ` [PATCH 2/3] iommu/arm-smmu-v3: Add an arm_smmu_tlb_inv_domain helper Nicolin Chen
2023-08-22  8:45   ` Nicolin Chen
2023-08-22  9:40   ` Robin Murphy
2023-08-22  9:40     ` Robin Murphy
2023-08-22 17:03     ` Nicolin Chen
2023-08-22 17:03       ` Nicolin Chen
2023-08-29 21:54       ` Robin Murphy
2023-08-29 21:54         ` Robin Murphy
2023-08-29 23:03         ` Nicolin Chen
2023-08-29 23:03           ` Nicolin Chen
2023-08-22  8:45 ` [PATCH 3/3] iommu/arm-smmu-v3: Add a max_tlbi_ops for __arm_smmu_tlb_inv_range() Nicolin Chen
2023-08-22  8:45   ` Nicolin Chen
2023-08-22  9:30   ` Robin Murphy
2023-08-22  9:30     ` Robin Murphy
2023-08-22 16:32     ` Nicolin Chen
2023-08-22 16:32       ` Nicolin Chen
2023-08-22 23:04       ` Nicolin Chen
2023-08-22 23:04         ` Nicolin Chen
2023-08-29 22:40         ` Robin Murphy
2023-08-29 22:40           ` Robin Murphy
2023-08-29 23:14           ` Nicolin Chen
2023-08-29 23:14             ` Nicolin Chen

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=cover.1692693557.git.nicolinc@nvidia.com \
    --to=nicolinc@nvidia.com \
    --cc=apopple@nvidia.com \
    --cc=iommu@lists.linux.dev \
    --cc=jean-philippe@linaro.org \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.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.