linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Daniel Walker <dwalker@codeaurora.org>
Cc: Andi Kleen <andi@firstfloor.org>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Zach Pfeffer <zpfeffer@codeaurora.org>,
	mel@csn.ul.ie, linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC 3/3] mm: iommu: The Virtual Contiguous Memory Manager
Date: Thu, 1 Jul 2010 21:38:50 +0200	[thread overview]
Message-ID: <20100701193850.GB3594@basil.fritz.box> (raw)
In-Reply-To: <1278012503.7738.17.camel@c-dwalke-linux.qualcomm.com>

On Thu, Jul 01, 2010 at 12:28:23PM -0700, Daniel Walker wrote:
> On Thu, 2010-07-01 at 20:02 +0200, Andi Kleen wrote:
> > > What license (name/type) is this?
> > 
> > IANAL, but AFAIK standard wisdom is that "disclaimer in the documentation
> > and/or other materials provided" is generally not acceptable for Linux
> > because it's an excessive burden for all distributors.
> 
> It's the BSD license ..

It's the old version of the BSD license that noone uses anymore because of its ]
problems: it's really a unreasonable burden to include hundreds or thousands of 
attributions for every contributor in every printed manual you ship.

The BSDs have all switched to the "Clause 2" (without this one) because 
of this.

> 
> > 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.

-Andi
-- 
ak@linux.intel.com -- Speaking for myself only.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-07-01 19:38 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-30  5:55 [RFC 1/3] mm: iommu: An API to unify IOMMU, CPU and device memory management Zach Pfeffer
2010-06-30  5:55 ` [RFC 2/3] mm: iommu: A physical allocator for the VCMM Zach Pfeffer
2010-06-30  5:55 ` [RFC 3/3] mm: iommu: The Virtual Contiguous Memory Manager Zach Pfeffer
2010-07-01 17:17   ` Randy Dunlap
2010-07-01 18:02     ` Andi Kleen
2010-07-01 19:28       ` Daniel Walker
2010-07-01 19:38         ` Andi Kleen [this message]
2010-07-01 19:42           ` Daniel Walker
2010-07-01 22:15             ` Hari Kanigeri
2010-07-02  7:09               ` Zach Pfeffer
2010-07-10 14:36                 ` Joerg Roedel
2010-07-13  5:21                   ` Zach Pfeffer
2010-07-14 19:34                     ` Joerg Roedel
2010-07-15  1:18                       ` Zach Pfeffer
2010-07-01 22:00           ` Zach Pfeffer
2010-07-01 22:05             ` Daniel Walker
2010-07-02  7:33               ` Zach Pfeffer
2010-07-10 14:56                 ` Joerg Roedel
2010-07-13  5:46                   ` Zach Pfeffer
2010-07-13  5:59                     ` FUJITA Tomonori
2010-07-13  8:20                       ` Alan Cox
2010-07-13  8:30                         ` FUJITA Tomonori
2010-07-13  8:42                           ` Alan Cox
2010-07-13  8:45                             ` FUJITA Tomonori
2010-07-13  9:02                               ` Russell King - ARM Linux
2010-07-14  1:59                                 ` FUJITA Tomonori
2010-07-22  3:50                                   ` Zach Pfeffer
2010-07-22  4:47                                     ` FUJITA Tomonori
2010-07-22 16:33                                       ` Zach Pfeffer
2010-07-22  7:51                                     ` Russell King - ARM Linux
2010-07-22 16:13                                       ` Zach Pfeffer
2010-07-13 12:06                       ` Zach Pfeffer
2010-07-01 22:51             ` Hari Kanigeri
2010-07-02  7:29               ` Zach Pfeffer
2010-07-01 23:00             ` Andi Kleen
2010-07-02  6:17               ` Zach Pfeffer
2010-07-02  8:22                 ` Andi Kleen
2010-07-02 18:42                   ` Zach Pfeffer
2010-07-10 15:11                 ` Joerg Roedel
2010-07-13  5:52                   ` Zach Pfeffer
2010-07-03  6:36               ` Zach Pfeffer
2010-07-10 14:54             ` Joerg Roedel
2010-07-13  5:27               ` Zach Pfeffer
2010-07-01 20:59     ` Paul Walmsley
2010-07-01 21:48       ` Randy Dunlap
2010-06-30 23:40 ` [RFC 1/3] mm: iommu: An API to unify IOMMU, CPU and device memory management Randy Dunlap
2010-07-01  7:16   ` Zach Pfeffer
2010-07-02  7:00     ` Paul Mundt

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=20100701193850.GB3594@basil.fritz.box \
    --to=andi@firstfloor.org \
    --cc=dwalker@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mel@csn.ul.ie \
    --cc=randy.dunlap@oracle.com \
    --cc=zpfeffer@codeaurora.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).