linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Sowmini Varadhan <sowmini.varadhan@oracle.com>
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 v5 RFC 0/3] Generic IOMMU pooled allocator
Date: Mon, 23 Mar 2015 10:32:29 +1100	[thread overview]
Message-ID: <1427067149.4770.209.camel@kernel.crashing.org> (raw)
In-Reply-To: <cover.1426986386.git.sowmini.varadhan@oracle.com>

On Sun, 2015-03-22 at 15:22 -0400, Sowmini Varadhan wrote:
> Follows up on the feedback in the thread at
>   http://www.spinics.net/lists/sparclinux/msg13493.html
> 
> - removed ->cookie_to_index and ->demap indirection from the iommu_tbl_ops
>   The caller needs to call these functions as needed, before invoking
>   the generic arena allocator functions.
> 
> - added the "skip_span_boundary" argument to iommu_tbl_pool_init() for
>   those callers like LDC which do no care about span boundary checks.

Thanks. I'll try to look in depth some time this week, but poke me if
you don't hear from me, I'm a bit swamped at the moment. In the
meantime, Alexey might have some bandwidth to also check it out.

Cheers,
Ben.

      parent reply	other threads:[~2015-03-22 23:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-22 19:22 [PATCH v5 RFC 0/3] Generic IOMMU pooled allocator Sowmini Varadhan
2015-03-22 19:22 ` [PATCH v5 RFC 1/3] sparc: Break up monolithic iommu table/lock into finer graularity pools and lock Sowmini Varadhan
2015-03-22 19:22 ` [PATCH v5 RFC 2/3] sparc: Make sparc64 use scalable lib/iommu-common.c functions Sowmini Varadhan
2015-03-22 19:22 ` [PATCH v5 RFC 3/3] sparc: Make LDC use common iommu poll management functions Sowmini Varadhan
2015-03-22 23:32 ` Benjamin Herrenschmidt [this message]

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=1427067149.4770.209.camel@kernel.crashing.org \
    --to=benh@kernel.crashing.org \
    --cc=aik@au1.ibm.com \
    --cc=anton@au1.ibm.com \
    --cc=davem@davemloft.net \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.org \
    --cc=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 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).