From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: aik@au1.ibm.com, anton@au1.ibm.com, paulus@samba.org,
sparclinux@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
davem@davemloft.net
Subject: Re: [PATCH v8 RFC 1/3] sparc: Break up monolithic iommu table/lock into finer graularity pools and lock
Date: Thu, 2 Apr 2015 17:54:53 -0400 [thread overview]
Message-ID: <20150402215453.GB15680@oracle.com> (raw)
In-Reply-To: <1428008044.20500.272.camel@kernel.crashing.org>
the other question that comes to my mind is: the whole lazy_flush
optimization probably works best when there is exactly one pool,
and no large pools. In most other cases, we'd end up doing a lazy_flush
when we wrap within our pool itself, losing the benefit of that
optimization.
Given that the lazy_flush is mostly there to avoid regressions for
the older sun4u architectures (which have other hardware bottlenecks
anyway), and this code is rapidly getting messy, does it make sense
to constrain the lazy_flush check to only apply for the 1-pool,
no-large-pool case?
next prev parent reply other threads:[~2015-04-02 21:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 14:40 [PATCH v8 RFC 0/3] Generic IOMMU pooled allocator Sowmini Varadhan
2015-03-31 14:40 ` [PATCH v8 RFC 1/3] sparc: Break up monolithic iommu table/lock into finer graularity pools and lock Sowmini Varadhan
2015-03-31 15:15 ` David Laight
2015-03-31 15:25 ` Sowmini Varadhan
2015-04-02 20:54 ` Benjamin Herrenschmidt
2015-04-02 21:43 ` Sowmini Varadhan
2015-04-02 21:57 ` Benjamin Herrenschmidt
2015-04-02 22:01 ` Benjamin Herrenschmidt
2015-04-02 22:02 ` Benjamin Herrenschmidt
2015-04-02 22:15 ` Sowmini Varadhan
2015-04-02 22:19 ` Benjamin Herrenschmidt
2015-04-02 21:54 ` Sowmini Varadhan [this message]
2015-04-02 22:08 ` Benjamin Herrenschmidt
2015-04-03 0:42 ` David Miller
2015-04-03 18:28 ` Sowmini Varadhan
2015-04-03 21:06 ` Benjamin Herrenschmidt
2015-04-03 21:51 ` Sowmini Varadhan
2015-04-04 11:27 ` Sowmini Varadhan
2015-04-04 13:33 ` Benjamin Herrenschmidt
2015-03-31 14:40 ` [PATCH v8 RFC 2/3] sparc: Make sparc64 use scalable lib/iommu-common.c functions Sowmini Varadhan
2015-03-31 14:40 ` [PATCH v8 RFC 3/3] sparc: Make LDC use common iommu poll management functions Sowmini Varadhan
2015-03-31 18:06 ` [PATCH v8 RFC 0/3] Generic IOMMU pooled allocator Sowmini Varadhan
2015-03-31 18:08 ` David Miller
2015-04-01 1:01 ` Benjamin Herrenschmidt
2015-04-01 1:08 ` Sowmini Varadhan
2015-04-01 3:12 ` David Miller
2015-04-02 12:51 ` Sowmini Varadhan
2015-04-02 16:21 ` David Miller
2015-04-02 20:22 ` Benjamin Herrenschmidt
2015-04-02 20:52 ` Benjamin Herrenschmidt
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=20150402215453.GB15680@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=aik@au1.ibm.com \
--cc=anton@au1.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).