From: Ming Lei <ming.lei@redhat.com>
To: John Garry <john.garry@huawei.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
iommu@lists.linux-foundation.org, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [bug report] iommu_dma_unmap_sg() is very slow then running IO from remote numa node
Date: Wed, 28 Jul 2021 23:17:20 +0800 [thread overview]
Message-ID: <YQF1AKS6Y14dLU/A@T590> (raw)
In-Reply-To: <ead87bf2-ddfa-eb67-db44-9619c6cdb714@huawei.com>
On Wed, Jul 28, 2021 at 11:38:18AM +0100, John Garry wrote:
> On 28/07/2021 02:32, Ming Lei wrote:
> > On Mon, Jul 26, 2021 at 3:51 PM John Garry<john.garry@huawei.com> wrote:
> > > On 23/07/2021 11:21, Ming Lei wrote:
> > > > > Thanks, I was also going to suggest the latter, since it's what
> > > > > arm_smmu_cmdq_issue_cmdlist() does with IRQs masked that should be most
> > > > > indicative of where the slowness most likely stems from.
> > > > The improvement from 'iommu.strict=0' is very small:
> > > >
> > > Have you tried turning off the IOMMU to ensure that this is really just
> > > an IOMMU problem?
> > >
> > > You can try setting CONFIG_ARM_SMMU_V3=n in the defconfig or passing
> > > cmdline param iommu.passthrough=1 to bypass the the SMMU (equivalent to
> > > disabling for kernel drivers).
> > Bypassing SMMU via iommu.passthrough=1 basically doesn't make a difference
> > on this issue.
>
> A ~90% throughput drop still seems to me to be too high to be a software
> issue. More so since I don't see similar on my system. And that throughput
> drop does not lead to a total CPU usage drop, from the fio log.
>
> Do you know if anyone has run memory benchmark tests on this board to find
> out NUMA effect? I think lmbench or stream could be used for this.
https://lore.kernel.org/lkml/YOhbc5C47IzC893B@T590/
--
Ming
WARNING: multiple messages have this Message-ID (diff)
From: Ming Lei <ming.lei@redhat.com>
To: John Garry <john.garry@huawei.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
iommu@lists.linux-foundation.org, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [bug report] iommu_dma_unmap_sg() is very slow then running IO from remote numa node
Date: Wed, 28 Jul 2021 23:17:20 +0800 [thread overview]
Message-ID: <YQF1AKS6Y14dLU/A@T590> (raw)
In-Reply-To: <ead87bf2-ddfa-eb67-db44-9619c6cdb714@huawei.com>
On Wed, Jul 28, 2021 at 11:38:18AM +0100, John Garry wrote:
> On 28/07/2021 02:32, Ming Lei wrote:
> > On Mon, Jul 26, 2021 at 3:51 PM John Garry<john.garry@huawei.com> wrote:
> > > On 23/07/2021 11:21, Ming Lei wrote:
> > > > > Thanks, I was also going to suggest the latter, since it's what
> > > > > arm_smmu_cmdq_issue_cmdlist() does with IRQs masked that should be most
> > > > > indicative of where the slowness most likely stems from.
> > > > The improvement from 'iommu.strict=0' is very small:
> > > >
> > > Have you tried turning off the IOMMU to ensure that this is really just
> > > an IOMMU problem?
> > >
> > > You can try setting CONFIG_ARM_SMMU_V3=n in the defconfig or passing
> > > cmdline param iommu.passthrough=1 to bypass the the SMMU (equivalent to
> > > disabling for kernel drivers).
> > Bypassing SMMU via iommu.passthrough=1 basically doesn't make a difference
> > on this issue.
>
> A ~90% throughput drop still seems to me to be too high to be a software
> issue. More so since I don't see similar on my system. And that throughput
> drop does not lead to a total CPU usage drop, from the fio log.
>
> Do you know if anyone has run memory benchmark tests on this board to find
> out NUMA effect? I think lmbench or stream could be used for this.
https://lore.kernel.org/lkml/YOhbc5C47IzC893B@T590/
--
Ming
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
WARNING: multiple messages have this Message-ID (diff)
From: Ming Lei <ming.lei@redhat.com>
To: John Garry <john.garry@huawei.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
iommu@lists.linux-foundation.org, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [bug report] iommu_dma_unmap_sg() is very slow then running IO from remote numa node
Date: Wed, 28 Jul 2021 23:17:20 +0800 [thread overview]
Message-ID: <YQF1AKS6Y14dLU/A@T590> (raw)
In-Reply-To: <ead87bf2-ddfa-eb67-db44-9619c6cdb714@huawei.com>
On Wed, Jul 28, 2021 at 11:38:18AM +0100, John Garry wrote:
> On 28/07/2021 02:32, Ming Lei wrote:
> > On Mon, Jul 26, 2021 at 3:51 PM John Garry<john.garry@huawei.com> wrote:
> > > On 23/07/2021 11:21, Ming Lei wrote:
> > > > > Thanks, I was also going to suggest the latter, since it's what
> > > > > arm_smmu_cmdq_issue_cmdlist() does with IRQs masked that should be most
> > > > > indicative of where the slowness most likely stems from.
> > > > The improvement from 'iommu.strict=0' is very small:
> > > >
> > > Have you tried turning off the IOMMU to ensure that this is really just
> > > an IOMMU problem?
> > >
> > > You can try setting CONFIG_ARM_SMMU_V3=n in the defconfig or passing
> > > cmdline param iommu.passthrough=1 to bypass the the SMMU (equivalent to
> > > disabling for kernel drivers).
> > Bypassing SMMU via iommu.passthrough=1 basically doesn't make a difference
> > on this issue.
>
> A ~90% throughput drop still seems to me to be too high to be a software
> issue. More so since I don't see similar on my system. And that throughput
> drop does not lead to a total CPU usage drop, from the fio log.
>
> Do you know if anyone has run memory benchmark tests on this board to find
> out NUMA effect? I think lmbench or stream could be used for this.
https://lore.kernel.org/lkml/YOhbc5C47IzC893B@T590/
--
Ming
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Ming Lei <ming.lei@redhat.com>
To: John Garry <john.garry@huawei.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
iommu@lists.linux-foundation.org, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [bug report] iommu_dma_unmap_sg() is very slow then running IO from remote numa node
Date: Wed, 28 Jul 2021 23:17:20 +0800 [thread overview]
Message-ID: <YQF1AKS6Y14dLU/A@T590> (raw)
In-Reply-To: <ead87bf2-ddfa-eb67-db44-9619c6cdb714@huawei.com>
On Wed, Jul 28, 2021 at 11:38:18AM +0100, John Garry wrote:
> On 28/07/2021 02:32, Ming Lei wrote:
> > On Mon, Jul 26, 2021 at 3:51 PM John Garry<john.garry@huawei.com> wrote:
> > > On 23/07/2021 11:21, Ming Lei wrote:
> > > > > Thanks, I was also going to suggest the latter, since it's what
> > > > > arm_smmu_cmdq_issue_cmdlist() does with IRQs masked that should be most
> > > > > indicative of where the slowness most likely stems from.
> > > > The improvement from 'iommu.strict=0' is very small:
> > > >
> > > Have you tried turning off the IOMMU to ensure that this is really just
> > > an IOMMU problem?
> > >
> > > You can try setting CONFIG_ARM_SMMU_V3=n in the defconfig or passing
> > > cmdline param iommu.passthrough=1 to bypass the the SMMU (equivalent to
> > > disabling for kernel drivers).
> > Bypassing SMMU via iommu.passthrough=1 basically doesn't make a difference
> > on this issue.
>
> A ~90% throughput drop still seems to me to be too high to be a software
> issue. More so since I don't see similar on my system. And that throughput
> drop does not lead to a total CPU usage drop, from the fio log.
>
> Do you know if anyone has run memory benchmark tests on this board to find
> out NUMA effect? I think lmbench or stream could be used for this.
https://lore.kernel.org/lkml/YOhbc5C47IzC893B@T590/
--
Ming
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-07-28 15:17 UTC|newest]
Thread overview: 120+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 8:38 [bug report] iommu_dma_unmap_sg() is very slow then running IO from remote numa node Ming Lei
2021-07-09 8:38 ` Ming Lei
2021-07-09 8:38 ` Ming Lei
2021-07-09 8:38 ` Ming Lei
2021-07-09 10:16 ` Russell King (Oracle)
2021-07-09 10:16 ` Russell King (Oracle)
2021-07-09 10:16 ` Russell King (Oracle)
2021-07-09 10:16 ` Russell King (Oracle)
2021-07-09 14:21 ` Ming Lei
2021-07-09 14:21 ` Ming Lei
2021-07-09 14:21 ` Ming Lei
2021-07-09 14:21 ` Ming Lei
2021-07-09 10:26 ` Robin Murphy
2021-07-09 10:26 ` Robin Murphy
2021-07-09 10:26 ` Robin Murphy
2021-07-09 10:26 ` Robin Murphy
2021-07-09 11:04 ` John Garry
2021-07-09 11:04 ` John Garry
2021-07-09 11:04 ` John Garry
2021-07-09 11:04 ` John Garry
2021-07-09 12:34 ` Robin Murphy
2021-07-09 12:34 ` Robin Murphy
2021-07-09 12:34 ` Robin Murphy
2021-07-09 12:34 ` Robin Murphy
2021-07-09 14:24 ` Ming Lei
2021-07-09 14:24 ` Ming Lei
2021-07-09 14:24 ` Ming Lei
2021-07-09 14:24 ` Ming Lei
2021-07-19 16:14 ` John Garry
2021-07-19 16:14 ` John Garry
2021-07-19 16:14 ` John Garry
2021-07-19 16:14 ` John Garry
2021-07-21 1:40 ` Ming Lei
2021-07-21 1:40 ` Ming Lei
2021-07-21 1:40 ` Ming Lei
2021-07-21 1:40 ` Ming Lei
2021-07-21 9:23 ` John Garry
2021-07-21 9:23 ` John Garry
2021-07-21 9:23 ` John Garry
2021-07-21 9:23 ` John Garry
2021-07-21 9:59 ` Ming Lei
2021-07-21 9:59 ` Ming Lei
2021-07-21 9:59 ` Ming Lei
2021-07-21 9:59 ` Ming Lei
2021-07-21 11:07 ` John Garry
2021-07-21 11:07 ` John Garry
2021-07-21 11:07 ` John Garry
2021-07-21 11:07 ` John Garry
2021-07-21 11:58 ` Ming Lei
2021-07-21 11:58 ` Ming Lei
2021-07-21 11:58 ` Ming Lei
2021-07-21 11:58 ` Ming Lei
2021-07-22 7:58 ` Ming Lei
2021-07-22 7:58 ` Ming Lei
2021-07-22 7:58 ` Ming Lei
2021-07-22 7:58 ` Ming Lei
2021-07-22 10:05 ` John Garry
2021-07-22 10:05 ` John Garry
2021-07-22 10:05 ` John Garry
2021-07-22 10:05 ` John Garry
2021-07-22 10:19 ` Ming Lei
2021-07-22 10:19 ` Ming Lei
2021-07-22 10:19 ` Ming Lei
2021-07-22 10:19 ` Ming Lei
2021-07-22 11:12 ` John Garry
2021-07-22 11:12 ` John Garry
2021-07-22 11:12 ` John Garry
2021-07-22 11:12 ` John Garry
2021-07-22 12:53 ` Marc Zyngier
2021-07-22 12:53 ` Marc Zyngier
2021-07-22 12:53 ` Marc Zyngier
2021-07-22 12:53 ` Marc Zyngier
2021-07-22 13:54 ` John Garry
2021-07-22 13:54 ` John Garry
2021-07-22 13:54 ` John Garry
2021-07-22 13:54 ` John Garry
2021-07-22 15:54 ` Ming Lei
2021-07-22 15:54 ` Ming Lei
2021-07-22 15:54 ` Ming Lei
2021-07-22 15:54 ` Ming Lei
2021-07-22 17:40 ` Robin Murphy
2021-07-22 17:40 ` Robin Murphy
2021-07-22 17:40 ` Robin Murphy
2021-07-22 17:40 ` Robin Murphy
2021-07-23 10:21 ` Ming Lei
2021-07-23 10:21 ` Ming Lei
2021-07-23 10:21 ` Ming Lei
2021-07-23 10:21 ` Ming Lei
2021-07-26 7:51 ` John Garry
2021-07-26 7:51 ` John Garry
2021-07-26 7:51 ` John Garry
2021-07-26 7:51 ` John Garry
2021-07-28 1:32 ` Ming Lei
2021-07-28 1:32 ` Ming Lei
2021-07-28 1:32 ` Ming Lei
2021-07-28 1:32 ` Ming Lei
2021-07-28 10:38 ` John Garry
2021-07-28 10:38 ` John Garry
2021-07-28 10:38 ` John Garry
2021-07-28 10:38 ` John Garry
2021-07-28 15:17 ` Ming Lei [this message]
2021-07-28 15:17 ` Ming Lei
2021-07-28 15:17 ` Ming Lei
2021-07-28 15:17 ` Ming Lei
2021-07-28 15:39 ` Robin Murphy
2021-07-28 15:39 ` Robin Murphy
2021-07-28 15:39 ` Robin Murphy
2021-07-28 15:39 ` Robin Murphy
2021-08-10 9:36 ` John Garry
2021-08-10 9:36 ` John Garry
2021-08-10 9:36 ` John Garry
2021-08-10 9:36 ` John Garry
2021-08-10 10:35 ` Ming Lei
2021-08-10 10:35 ` Ming Lei
2021-08-10 10:35 ` Ming Lei
2021-08-10 10:35 ` Ming Lei
2021-07-27 17:08 ` Robin Murphy
2021-07-27 17:08 ` Robin Murphy
2021-07-27 17:08 ` Robin Murphy
2021-07-27 17:08 ` Robin Murphy
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=YQF1AKS6Y14dLU/A@T590 \
--to=ming.lei@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=john.garry@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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.