From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH RFC sparc] Break up iommu from monolithic lock for the map to multiple pools/locks
Date: Fri, 19 Dec 2014 18:31:33 +0000 [thread overview]
Message-ID: <20141219183133.GH4294@oracle.com> (raw)
In-Reply-To: <20141219151616.GB25248@oracle.com>
On (12/19/14 12:26), David Miller wrote:
>
> If this is such a better and more scalable algorithm for IOMMU
> arena DMA region allocation, then instead of one platform after
> another putting a private implementation under arch/, the generic
> IOMMU code should be adjusted instead.
>
> Right?
Then again, I just realized that you are talking about factorizing
common code across multiple architectures, instead of multiple drivers
within sparc.
yes, that would be even better.
I could look into that, but would need help from other arch experts for
help with extraction of the platform-dependant parts, implementation and
testing. Looks like pci-calgary_64.c also has an obvious copy of the
powerpc algorithm, and there are other *iommu.c implementations as well,
where the duplication may be there, but is not obvious (from cscope etc.).
--Sowmini
next prev parent reply other threads:[~2014-12-19 18:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 15:16 [PATCH RFC sparc] Break up iommu from monolithic lock for the map to multiple pools/locks Sowmini Varadhan
2014-12-19 17:26 ` David Miller
2014-12-19 17:29 ` Sowmini Varadhan
2014-12-19 18:31 ` Sowmini Varadhan [this message]
2014-12-19 19:57 ` David Miller
2014-12-19 20:06 ` Sowmini Varadhan
2014-12-19 20:24 ` David Miller
2014-12-19 20:44 ` Sowmini Varadhan
2014-12-19 20:56 ` David Miller
2014-12-19 22:06 ` 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=20141219183133.GH4294@oracle.com \
--to=sowmini.varadhan@oracle.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.