* Re: [PATCH v2 0/2] sparc: IOMMU pools for better scalability
2015-03-03 14:22 [PATCH v2 0/2] sparc: IOMMU pools for better scalability Sowmini Varadhan
@ 2015-03-03 22:15 ` David Miller
2015-03-04 19:10 ` Sowmini Varadhan
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: David Miller @ 2015-03-03 22:15 UTC (permalink / raw)
To: sparclinux
From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Date: Tue, 3 Mar 2015 09:22:02 -0500
>
> V2 version ofthis patch-set incorporates the feedback from
> http://marc.info/?l=linux-sparc&m\x142527471211108&w=2
> The sparc specific fields have been moved off into iommu_64.h,
> into struct iommu_sparc, leaving a minimalist struct iommu_table
> in the common functions..
Still have some sparc specific stuff in the generic header file.
For example, IOMMU_NUM_CTXS.
I don't see anything using cookie_to_index.
Furthermore, who so many TABS in the dma_4v_iommu_ops initializer?
Next, canonically "linux/" headers are included before "asm/" ones.
Please don't put "ifdef notyet" kind of stuff into your changes,
that is not appropriate. In any event, I want you to translate all
of the PCI DMA implementations, because it is the only way you can
show me that your abstractions are sufficient.
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [PATCH v2 0/2] sparc: IOMMU pools for better scalability
2015-03-03 14:22 [PATCH v2 0/2] sparc: IOMMU pools for better scalability Sowmini Varadhan
2015-03-03 22:15 ` David Miller
@ 2015-03-04 19:10 ` Sowmini Varadhan
2015-03-04 19:15 ` David Miller
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Sowmini Varadhan @ 2015-03-04 19:10 UTC (permalink / raw)
To: sparclinux
On (03/03/15 17:15), David Miller wrote:
>
> For example, IOMMU_NUM_CTXS.
>
> I don't see anything using cookie_to_index.
>
> Furthermore, who so many TABS in the dma_4v_iommu_ops initializer?
>
> Next, canonically "linux/" headers are included before "asm/" ones.
sure I can fix all of the above for v3. The cookie_to_index
comes from ldc_iommu conversion, which I had not added to the set
because it does nothing whatsoever for ldc perf, where we are only
dealing with an 8k map size, though I see the value of less code
duplication.
I'll add ldc to the v3 patch-set.
However..
> Please don't put "ifdef notyet" kind of stuff into your changes,
> that is not appropriate. In any event, I want you to translate all
> of the PCI DMA implementations, because it is the only way you can
> show me that your abstractions are sufficient.
That means I have to fix all kinds of dinosaurs in the neighborhood,
things like pci_fire, pci_schizo, pci_psycho, sun4u. Some of this
hardware was EOL'ed a long time ago. And the last time I remember
using a sun4u was back in 2008 (and even then, it was really not
very useful for any sort of non-trivial SMP/perf development).
But whatever floats your boat.
Just want to note that this will no longer be a simple 2-part patch set.
--Sowmini
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [PATCH v2 0/2] sparc: IOMMU pools for better scalability
2015-03-03 14:22 [PATCH v2 0/2] sparc: IOMMU pools for better scalability Sowmini Varadhan
2015-03-03 22:15 ` David Miller
2015-03-04 19:10 ` Sowmini Varadhan
@ 2015-03-04 19:15 ` David Miller
2015-03-04 19:32 ` David Ahern
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: David Miller @ 2015-03-04 19:15 UTC (permalink / raw)
To: sparclinux
From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Date: Wed, 4 Mar 2015 14:10:17 -0500
> On (03/03/15 17:15), David Miller wrote:
>> Please don't put "ifdef notyet" kind of stuff into your changes,
>> that is not appropriate. In any event, I want you to translate all
>> of the PCI DMA implementations, because it is the only way you can
>> show me that your abstractions are sufficient.
>
> That means I have to fix all kinds of dinosaurs in the neighborhood,
> things like pci_fire, pci_schizo, pci_psycho, sun4u. Some of this
> hardware was EOL'ed a long time ago. And the last time I remember
> using a sun4u was back in 2008 (and even then, it was really not
> very useful for any sort of non-trivial SMP/perf development).
>
> But whatever floats your boat.
It's a conversion that has to be done anyways, and otherwise you'll
have no idea whether your abstractions are sufficient or not.
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [PATCH v2 0/2] sparc: IOMMU pools for better scalability
2015-03-03 14:22 [PATCH v2 0/2] sparc: IOMMU pools for better scalability Sowmini Varadhan
` (2 preceding siblings ...)
2015-03-04 19:15 ` David Miller
@ 2015-03-04 19:32 ` David Ahern
2015-03-04 20:35 ` David Miller
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: David Ahern @ 2015-03-04 19:32 UTC (permalink / raw)
To: sparclinux
On 3/4/15 12:15 PM, David Miller wrote:
> From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
> Date: Wed, 4 Mar 2015 14:10:17 -0500
>
>> On (03/03/15 17:15), David Miller wrote:
>>> Please don't put "ifdef notyet" kind of stuff into your changes,
>>> that is not appropriate. In any event, I want you to translate all
>>> of the PCI DMA implementations, because it is the only way you can
>>> show me that your abstractions are sufficient.
>>
>> That means I have to fix all kinds of dinosaurs in the neighborhood,
>> things like pci_fire, pci_schizo, pci_psycho, sun4u. Some of this
>> hardware was EOL'ed a long time ago. And the last time I remember
>> using a sun4u was back in 2008 (and even then, it was really not
>> very useful for any sort of non-trivial SMP/perf development).
>>
>> But whatever floats your boat.
>
> It's a conversion that has to be done anyways, and otherwise you'll
> have no idea whether your abstractions are sufficient or not.
Doesn't that run the risk of breaking older platforms, which cannot
realistically be tested? Why not refactor the code such that old
platforms are not touched and focus on abstractions for modern h/w?
David
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [PATCH v2 0/2] sparc: IOMMU pools for better scalability
2015-03-03 14:22 [PATCH v2 0/2] sparc: IOMMU pools for better scalability Sowmini Varadhan
` (3 preceding siblings ...)
2015-03-04 19:32 ` David Ahern
@ 2015-03-04 20:35 ` David Miller
2015-03-04 20:37 ` David Miller
2015-03-04 20:55 ` Sowmini Varadhan
6 siblings, 0 replies; 8+ messages in thread
From: David Miller @ 2015-03-04 20:35 UTC (permalink / raw)
To: sparclinux
From: David Ahern <dsahern@gmail.com>
Date: Wed, 04 Mar 2015 12:32:32 -0700
> On 3/4/15 12:15 PM, David Miller wrote:
>> From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
>> Date: Wed, 4 Mar 2015 14:10:17 -0500
>>
>>> On (03/03/15 17:15), David Miller wrote:
>>>> Please don't put "ifdef notyet" kind of stuff into your changes,
>>>> that is not appropriate. In any event, I want you to translate all
>>>> of the PCI DMA implementations, because it is the only way you can
>>>> show me that your abstractions are sufficient.
>>>
>>> That means I have to fix all kinds of dinosaurs in the neighborhood,
>>> things like pci_fire, pci_schizo, pci_psycho, sun4u. Some of this
>>> hardware was EOL'ed a long time ago. And the last time I remember
>>> using a sun4u was back in 2008 (and even then, it was really not
>>> very useful for any sort of non-trivial SMP/perf development).
>>>
>>> But whatever floats your boat.
>>
>> It's a conversion that has to be done anyways, and otherwise you'll
>> have no idea whether your abstractions are sufficient or not.
>
> Doesn't that run the risk of breaking older platforms, which cannot
> realistically be tested? Why not refactor the code such that old
> platforms are not touched and focus on abstractions for modern h/w?
Are you kidding me? I have a sun4u sitting right under my desk, and
several more (all IOMMU variants) at my Seattle house, I'll test it
for you.
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [PATCH v2 0/2] sparc: IOMMU pools for better scalability
2015-03-03 14:22 [PATCH v2 0/2] sparc: IOMMU pools for better scalability Sowmini Varadhan
` (4 preceding siblings ...)
2015-03-04 20:35 ` David Miller
@ 2015-03-04 20:37 ` David Miller
2015-03-04 20:55 ` Sowmini Varadhan
6 siblings, 0 replies; 8+ messages in thread
From: David Miller @ 2015-03-04 20:37 UTC (permalink / raw)
To: sparclinux
From: David Miller <davem@davemloft.net>
Date: Wed, 04 Mar 2015 15:35:38 -0500 (EST)
> Are you kidding me? I have a sun4u sitting right under my desk, and
> several more (all IOMMU variants) at my Seattle house, I'll test it
> for you.
Furthermore, people like Meelis Roos are here testing sun4u based
sparc64 systems all the time.
People do actively use these systems, report bugs, and will help
us work on any regressions.
So please don't use this as an excuse to not implement things
properly. Just because Sun EOL'd the machine doesn't mean it's
not actively in use and supported by Linus.
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [PATCH v2 0/2] sparc: IOMMU pools for better scalability
2015-03-03 14:22 [PATCH v2 0/2] sparc: IOMMU pools for better scalability Sowmini Varadhan
` (5 preceding siblings ...)
2015-03-04 20:37 ` David Miller
@ 2015-03-04 20:55 ` Sowmini Varadhan
6 siblings, 0 replies; 8+ messages in thread
From: Sowmini Varadhan @ 2015-03-04 20:55 UTC (permalink / raw)
To: sparclinux
On (03/04/15 15:37), David Miller wrote:
> From: David Miller <davem@davemloft.net>
> Date: Wed, 04 Mar 2015 15:35:38 -0500 (EST)
>
> > Are you kidding me? I have a sun4u sitting right under my desk, and
> > several more (all IOMMU variants) at my Seattle house, I'll test it
> > for you.
Thanks for the offer, and I may take you up on it.
But at the moment I'm trying to see what we have in-house, so let me
pursue those chains first, and then ping this list if we need
additional coverage.
> Furthermore, people like Meelis Roos are here testing sun4u based
> sparc64 systems all the time.
>
> People do actively use these systems, report bugs, and will help
> us work on any regressions.
>
> So please don't use this as an excuse to not implement things
Understood.
--Sowmini
^ permalink raw reply [flat|nested] 8+ messages in thread