From: David Ahern <dsahern@gmail.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH v2 0/2] sparc: IOMMU pools for better scalability
Date: Wed, 04 Mar 2015 19:32:32 +0000 [thread overview]
Message-ID: <54F75DD0.2010902@gmail.com> (raw)
In-Reply-To: <20150303142202.GA7696@oracle.com>
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
next prev parent reply other threads:[~2015-03-04 19:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2015-03-04 20:35 ` David Miller
2015-03-04 20:37 ` David Miller
2015-03-04 20:55 ` Sowmini Varadhan
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=54F75DD0.2010902@gmail.com \
--to=dsahern@gmail.com \
--cc=sparclinux@vger.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.