public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: davem@redhat.com, anton@samba.org, linux-arch@vger.kernel.org
Subject: Re: pci_map_single return value
Date: Fri, 19 Mar 2004 22:05:06 +0100	[thread overview]
Message-ID: <20040319220506.1718cc55.ak@suse.de> (raw)
In-Reply-To: <1079730090.1778.1.camel@mulgrave>

On 19 Mar 2004 16:01:29 -0500
James Bottomley <James.Bottomley@steeleye.com> wrote:

> On Fri, 2004-03-19 at 13:55, David S. Miller wrote:
> > I agree with your concerns, but I don't think I'd go that far.
> > 
> > This error return issue has been around far too long, years in fact.
> > We should make it easier to get this functionality into the tree, not
> > harder.
> > 
> > If there are extra knobs and stuff people need to do in order to what
> > effectively amounts to checking for kmalloc() returning NULL, they
> > are going to be less inclined to do the work.
> 
> I know.  My concern stems more from the fact that we have new
> architectures that have far fewer IOMMU resources.  The primary problem
> is x86-64 with only about 256MB of mapping space.  However on that arch,

Actually 64MB on many systems (128MB AGP aperture and 64MB of that is used 
for AGP)

There are kernel and BIOS options to increase it, but they are often not 
set. The kernel options cost memory and cannot be enabled by default.

> the IOMMU is disabled by default, so it isn't really a problem I
> suppose.

It is effectively disabled when you have ~3GB of memory, but when you have more
and a 32bit only device it will be enabled for that.

-Andi

  reply	other threads:[~2004-03-19 21:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20031212155752.GD17683@krispykreme>
     [not found] ` <20031212175104.07dc8444.ak@suse.de>
     [not found]   ` <20031212192131.GF17683@krispykreme>
     [not found]     ` <20031213220444.4c526afa.davem@redhat.com>
     [not found]       ` <20040102120121.GT28023@krispykreme>
     [not found]         ` <20040102133454.22daa451.ak@suse.de>
2004-03-19  0:14           ` pci_map_single return value Anton Blanchard
2004-03-19  0:41             ` David S. Miller
2004-03-19  0:55             ` Andrew Morton
2004-03-19  1:37               ` Anton Blanchard
2004-03-19 14:16                 ` James Bottomley
2004-03-19 16:57             ` James Bottomley
2004-03-19 18:55               ` David S. Miller
2004-03-19 21:01                 ` James Bottomley
2004-03-19 21:05                   ` Andi Kleen [this message]
2004-03-20  0:13                     ` James Bottomley

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=20040319220506.1718cc55.ak@suse.de \
    --to=ak@suse.de \
    --cc=James.Bottomley@steeleye.com \
    --cc=anton@samba.org \
    --cc=davem@redhat.com \
    --cc=linux-arch@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