[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1278013320.7738.19.camel@c-dwalke-linux.qualcomm.com>
Date: Thu, 01 Jul 2010 12:42:00 -0700
From: Daniel Walker <dwalker@...eaurora.org>
To: Andi Kleen <andi@...stfloor.org>
Cc: Randy Dunlap <randy.dunlap@...cle.com>,
Zach Pfeffer <zpfeffer@...eaurora.org>, mel@....ul.ie,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org, linux-omap@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC 3/3] mm: iommu: The Virtual Contiguous Memory Manager
On Thu, 2010-07-01 at 21:38 +0200, Andi Kleen wrote:
> >
> > > Also for me it's still quite unclear why we would want this code at all...
> > > It doesn't seem to do anything you couldn't do with the existing interfaces.
> >
> > I don't know all that much about what Zach's done here, but from what
> > he's said so far it looks like this help to manage lots of IOMMUs on a
> > single system.. On x86 it seems like there's not all that many IOMMUs in
> > comparison .. Zach mentioned 10 to 100 IOMMUs ..
>
> The current code can manage multiple IOMMUs fine.
He demonstrated the usage of his code in one of the emails he sent out
initially. Did you go over that, and what (or how many) step would you
use with the current code to do the same thing?
Daniel
--
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists