Re: [PATCH 0/8] io-pgtable lock removal

2017-07-07 Thread Will Deacon
On Thu, Jul 06, 2017 at 11:14:00AM -0700, Ray Jui wrote: > On 7/6/17 8:08 AM, Will Deacon wrote: > > On Wed, Jul 05, 2017 at 04:24:22PM -0700, Ray Jui wrote: > >> However, with the fix patch, I can still see the deadlock message when I > >> have > 32 iperf TX threads active in the system: > > > >

Re: [PATCH 0/8] io-pgtable lock removal

2017-07-06 Thread Ray Jui via iommu
Hi Will, On 7/6/17 8:08 AM, Will Deacon wrote: > Hi Ray, > > Thanks for testing this, and sorry it didn't help. > > On Wed, Jul 05, 2017 at 04:24:22PM -0700, Ray Jui wrote: >> On 7/5/17 1:41 AM, Will Deacon wrote: >>> On Tue, Jul 04, 2017 at 06:45:17PM -0700, Ray Jui wrote: Has anything fun

Re: [PATCH 0/8] io-pgtable lock removal

2017-07-06 Thread Will Deacon
Hi Ray, Thanks for testing this, and sorry it didn't help. On Wed, Jul 05, 2017 at 04:24:22PM -0700, Ray Jui wrote: > On 7/5/17 1:41 AM, Will Deacon wrote: > > On Tue, Jul 04, 2017 at 06:45:17PM -0700, Ray Jui wrote: > >> Has anything functionally changed between PATCH v2 and v1? I'm seeing a > >

Re: [PATCH 0/8] io-pgtable lock removal

2017-07-05 Thread Ray Jui via iommu
Hi Will, On 7/5/17 1:41 AM, Will Deacon wrote: > On Tue, Jul 04, 2017 at 06:45:17PM -0700, Ray Jui wrote: >> Hi Will/Robin, >> >> Has anything functionally changed between PATCH v2 and v1? I'm seeing a >> very different L2 throughput with v2 (in general a lot worse with v2 vs. >> v1); however, I'm

Re: [PATCH 0/8] io-pgtable lock removal

2017-07-05 Thread Will Deacon
On Tue, Jul 04, 2017 at 06:45:17PM -0700, Ray Jui wrote: > Hi Will/Robin, > > Has anything functionally changed between PATCH v2 and v1? I'm seeing a > very different L2 throughput with v2 (in general a lot worse with v2 vs. > v1); however, I'm currently unable to reproduce the TLB sync timed out

Re: [PATCH 0/8] io-pgtable lock removal

2017-07-04 Thread Ray Jui via iommu
Hi Will/Robin, Has anything functionally changed between PATCH v2 and v1? I'm seeing a very different L2 throughput with v2 (in general a lot worse with v2 vs. v1); however, I'm currently unable to reproduce the TLB sync timed out issue with v2 (without the patch from Will's email). It could also

Re: [PATCH 0/8] io-pgtable lock removal

2017-07-04 Thread Ray Jui via iommu
Hi Will, On 7/4/17 10:31 AM, Will Deacon wrote: > Ray, > > On Wed, Jun 28, 2017 at 10:02:35AM -0700, Ray Jui wrote: >> On 6/28/17 4:46 AM, Will Deacon wrote: >>> Robin and I have been bashing our heads against the tlb_sync_pending flag >>> this morning, and we reckon it could have something to do

Re: [PATCH 0/8] io-pgtable lock removal

2017-07-04 Thread Will Deacon
Ray, On Wed, Jun 28, 2017 at 10:02:35AM -0700, Ray Jui wrote: > On 6/28/17 4:46 AM, Will Deacon wrote: > > Robin and I have been bashing our heads against the tlb_sync_pending flag > > this morning, and we reckon it could have something to do with your timeouts > > on MMU-500. > > > > On Tue, Jun

Re: [PATCH 0/8] io-pgtable lock removal

2017-06-28 Thread Ray Jui via iommu
Hi Will/Robin, On 6/28/17 4:46 AM, Will Deacon wrote: > Hi Ray, > > Robin and I have been bashing our heads against the tlb_sync_pending flag > this morning, and we reckon it could have something to do with your timeouts > on MMU-500. > > On Tue, Jun 27, 2017 at 09:43:19AM -0700, Ray Jui wrote:

Re: [PATCH 0/8] io-pgtable lock removal

2017-06-28 Thread Will Deacon
Hi Ray, Robin and I have been bashing our heads against the tlb_sync_pending flag this morning, and we reckon it could have something to do with your timeouts on MMU-500. On Tue, Jun 27, 2017 at 09:43:19AM -0700, Ray Jui wrote: > >> Also, in a few occasions, I observed the following message durin

Re: [PATCH 0/8] io-pgtable lock removal

2017-06-27 Thread Ray Jui via iommu
Hi Robin, On 6/20/17 6:37 AM, Robin Murphy wrote: > On 15/06/17 01:40, Ray Jui wrote: >> Hi Robin, >> >> I have applied this patch series on top of v4.12-rc4, and ran various >> Ethernet and NVMf target throughput tests on it. >> >> To give you some background of my setup: >> >> The system is a AR

Re: [PATCH 0/8] io-pgtable lock removal

2017-06-21 Thread Joerg Roedel
On Wed, Jun 14, 2017 at 05:40:30PM -0700, Ray Jui wrote: > With the NVMf target test with 4 SSDs, fio based test, random read, 4k, > 8 jobs: > > Without IOMMU: > > IOPS = 1080K > > With IOMMU, but without your latest patch: > > IOPS = 520K > > With IOMMU and your latest patch: > > IOPS = 500K

Re: [PATCH 0/8] io-pgtable lock removal

2017-06-20 Thread Robin Murphy
On 15/06/17 01:40, Ray Jui wrote: > Hi Robin, > > I have applied this patch series on top of v4.12-rc4, and ran various > Ethernet and NVMf target throughput tests on it. > > To give you some background of my setup: > > The system is a ARMv8 based system with 8 cores. It has various PCIe > root

Re: [PATCH 0/8] io-pgtable lock removal

2017-06-15 Thread John Garry
On 15/06/2017 01:40, Ray Jui via iommu wrote: Hi Robin, wangzhou tested this patchset on our SMMUv3-based development board with a 10G PCI NIC card. Currently we see a ~17% performance (throughput) drop when enabling the SMMU, but only a ~8% drop with your patchset. FYI, for our integrated

Re: [PATCH 0/8] io-pgtable lock removal

2017-06-14 Thread Ray Jui via iommu
Hi Robin, I have applied this patch series on top of v4.12-rc4, and ran various Ethernet and NVMf target throughput tests on it. To give you some background of my setup: The system is a ARMv8 based system with 8 cores. It has various PCIe root complexes that can be used to connect to PCIe endpoi

Re: [PATCH 0/8] io-pgtable lock removal

2017-06-09 Thread Nate Watterson
Hi Robin, On 6/8/2017 7:51 AM, Robin Murphy wrote: Hi all, Here's the cleaned up nominally-final version of the patches everybody's keen to see. #1 is just a non-critical thing-I-spotted-in-passing fix, #2-#4 do some preparatory work (and bid farewell to everyone's least favourite bit of code,

[PATCH 0/8] io-pgtable lock removal

2017-06-08 Thread Robin Murphy
Hi all, Here's the cleaned up nominally-final version of the patches everybody's keen to see. #1 is just a non-critical thing-I-spotted-in-passing fix, #2-#4 do some preparatory work (and bid farewell to everyone's least favourite bit of code, hooray!), and #5-#8 do the dirty deed itself. The bra