From: joro@8bytes.org (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 8/9] iommu: add support for ARM Ltd. System MMU architecture
Date: Fri, 21 Jun 2013 17:30:44 +0200 [thread overview]
Message-ID: <20130621153044.GL11309@8bytes.org> (raw)
In-Reply-To: <20130621150006.GG7766@mudshark.cambridge.arm.com>
On Fri, Jun 21, 2013 at 04:00:06PM +0100, Will Deacon wrote:
> Damn, I was hoping to avoid locking on the map path. In fact, this is a good
> argument to go with your suggestion below (otherwise I'd need to use
> reader/writer locks which seem to be frowned on).
You should look into using rcu-lists instead. You still need a lock, but
only when you actually manipulating the lists. For traversing them it is
sufficient to take the rcu_read_lock() which has very low overhead.
Joerg
next prev parent reply other threads:[~2013-06-21 15:30 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 18:34 [PATCH 0/9] Add support for ARM SMMU architectures 1 and 2 Will Deacon
2013-06-10 18:34 ` [PATCH 1/9] dma: pl330: rip out broken, redundant ID probing Will Deacon
2013-06-11 4:40 ` Jassi Brar
2013-06-11 8:45 ` Will Deacon
2013-06-11 22:31 ` Grant Likely
2013-06-12 5:31 ` Vinod Koul
2013-06-10 18:34 ` [PATCH 2/9] dma: pl330: use dma_addr_t for describing bus addresses Will Deacon
2013-06-11 4:39 ` Jassi Brar
2013-06-11 22:32 ` Grant Likely
[not found] ` <CAJe_ZheKMVQgq42Vx5N1TXXdgFJ2sp50ixU30A7beXhmSVHnZQ@mail.gmail.com>
2013-06-12 5:31 ` Vinod Koul
2013-06-10 18:34 ` [PATCH 3/9] ARM: dma-mapping: convert DMA direction into IOMMU protection attributes Will Deacon
2013-06-19 8:37 ` Marek Szyprowski
2013-06-19 8:52 ` Will Deacon
2013-06-19 8:57 ` Marek Szyprowski
2013-06-25 10:12 ` Hiroshi Doyu
2013-06-25 11:37 ` Will Deacon
2013-06-25 11:52 ` Hiroshi Doyu
2013-06-25 12:34 ` Will Deacon
2013-06-10 18:34 ` [PATCH 4/9] ARM: dma-mapping: NULLify dev->archdata.mapping pointer on detach Will Deacon
2013-06-11 5:34 ` Hiroshi Doyu
2013-06-11 8:50 ` Will Deacon
2013-06-11 9:39 ` Hiroshi Doyu
2013-06-19 8:59 ` Marek Szyprowski
2013-06-10 18:34 ` [PATCH 5/9] arm64: pgtable: use pte_index instead of __pte_index Will Deacon
2013-06-10 18:34 ` [PATCH 6/9] arm64: device: add iommu pointer to device archdata Will Deacon
2013-06-10 18:34 ` [PATCH 7/9] documentation: iommu: add description of ARM System MMU binding Will Deacon
2013-06-12 8:44 ` Grant Likely
2013-06-20 20:08 ` Joerg Roedel
2013-06-21 9:57 ` Will Deacon
2013-06-21 13:55 ` Joerg Roedel
2013-06-21 16:41 ` Will Deacon
2013-06-25 19:18 ` Stuart Yoder
2013-06-26 13:39 ` Will Deacon
2013-06-26 16:19 ` Stuart Yoder
2013-06-26 17:42 ` Will Deacon
2013-06-27 18:22 ` Stuart Yoder
2013-06-28 9:06 ` Will Deacon
2013-06-28 16:03 ` Stuart Yoder
2013-06-10 18:34 ` [PATCH 8/9] iommu: add support for ARM Ltd. System MMU architecture Will Deacon
2013-06-20 21:26 ` Joerg Roedel
2013-06-21 10:23 ` Will Deacon
2013-06-21 14:13 ` Joerg Roedel
2013-06-21 15:00 ` Will Deacon
2013-06-21 15:30 ` Joerg Roedel [this message]
2013-06-21 16:40 ` Will Deacon
2013-06-10 18:34 ` [PATCH 9/9] MAINTAINERS: add entry for ARM system MMU driver Will Deacon
2013-06-12 8:45 ` Grant Likely
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=20130621153044.GL11309@8bytes.org \
--to=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.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).