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
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
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
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
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:
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
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
Hi Robin,
On 6/6/2017 3:02 AM, Robin Murphy wrote:
I've currently got some experimental patches pushed out here:
git://linux-arm.org/linux-rm iommu/pgtable
So far, there's still one silly bug (which doesn't affect DMA ops usage)
and an awkward race for non-coherent table walks which wil
Hi Will/Robin,
Just want to check with you on this again. Do you have a very rough
timeline on when the excessive locking in the IOMMU driver may be fixed
(so we can restore expected up to 95% performance)?
Thanks,
Ray
On 5/31/17 10:32 AM, Ray Jui wrote:
> Hi Will,
>
> On 5/31/17 5:44 AM, Wil
Hi Will,
On 5/31/17 5:44 AM, Will Deacon wrote:
> On Tue, May 30, 2017 at 11:13:36PM -0700, Ray Jui wrote:
>> I did a little more digging myself and I think I now understand what you
>> meant by identity mapping, i.e., configuring the MMU-500 with 1:1 mapping
>> between the DMA address and the IOV
Hi Marc/Robin/Will,
I did a little more digging myself and I think I now understand what you
meant by identity mapping, i.e., configuring the MMU-500 with 1:1
mapping between the DMA address and the IOVA address.
I think that should work. In the end, due to this MSI write parsing
issue in ou
Hi Marc/Robin/Will,
On 5/30/17 10:27 AM, Marc Zyngier wrote:
> On 30/05/17 18:16, Ray Jui wrote:
>> Hi Marc,
>>
>> On 5/30/17 9:59 AM, Marc Zyngier wrote:
>>> On 30/05/17 17:49, Ray Jui wrote:
Hi Will,
On 5/30/17 8:14 AM, Will Deacon wrote:
> On Mon, May 29, 2017 at 06:18:45PM -
Hi Marc,
On 5/30/17 9:59 AM, Marc Zyngier wrote:
> On 30/05/17 17:49, Ray Jui wrote:
>> Hi Will,
>>
>> On 5/30/17 8:14 AM, Will Deacon wrote:
>>> On Mon, May 29, 2017 at 06:18:45PM -0700, Ray Jui wrote:
I'm writing to check with you to see if the latest arm-smmu.c driver in
v4.12-rc Linu
Hi Will,
On 5/30/17 8:14 AM, Will Deacon wrote:
> On Mon, May 29, 2017 at 06:18:45PM -0700, Ray Jui wrote:
>> I'm writing to check with you to see if the latest arm-smmu.c driver in
>> v4.12-rc Linux for smmu-500 can support mapping that is only specific to
>> a particular physical address range w
Hi All,
I'm writing to check with you to see if the latest arm-smmu.c driver in
v4.12-rc Linux for smmu-500 can support mapping that is only specific to
a particular physical address range while leave the rest still to be
handled by the client device. I believe this can already be supported by
the
15 matches
Mail list logo
