linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Johannes Erdfelt <johannes@erdfelt.com>
Cc: "David S. Miller" <davem@redhat.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: struct page to 36 (or 64) bit bus address?
Date: Sat, 11 Aug 2001 17:56:26 +0200	[thread overview]
Message-ID: <20010811175626.O19169@athlon.random> (raw)
In-Reply-To: <20010809151022.C1575@sventech.com> <E15UvLO-0007tH-00@the-village.bc.nu> <15218.61869.424038.30544@pizda.ninka.net> <20010809163531.D1575@sventech.com>
In-Reply-To: <20010809163531.D1575@sventech.com>; from johannes@erdfelt.com on Thu, Aug 09, 2001 at 04:35:32PM -0400

On Thu, Aug 09, 2001 at 04:35:32PM -0400, Johannes Erdfelt wrote:
> It's not a big deal. It's just less efficient which isn't the end of the
> world.

It's not only less efficient, your machine is going to crash as soon as
you ask the iommu to map some giga of ram with the current state of
drivers (the API says that if you get null out of the map call you
should fallback, but no driver checks for this null retval and so in
turn they're all prone to crash, not going to be fixed in 2.4 I guess).
So try to reduce as much as possible the number of simultaneous pci
mappings and it will probably not crash.

Andrea

  parent reply	other threads:[~2001-08-11 15:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-09 18:40 struct page to 36 (or 64) bit bus address? Johannes Erdfelt
2001-08-09 19:09 ` Alan Cox
2001-08-09 19:10   ` Johannes Erdfelt
2001-08-09 19:19     ` Alan Cox
2001-08-09 20:25     ` David S. Miller
2001-08-09 20:35       ` Johannes Erdfelt
2001-08-10  7:00         ` Gerd Knorr
2001-08-10  7:56           ` Johannes Erdfelt
2001-08-10 21:58         ` David S. Miller
2001-08-11  7:09           ` Gerd Knorr
2001-08-12 10:49             ` Write Combining (Write Coalescing) on memory mapped I/O on IA64 Steffen Persvold
2001-08-11 15:32           ` struct page to 36 (or 64) bit bus address? Jens Axboe
2001-08-11 15:56         ` Andrea Arcangeli [this message]
2001-08-11 16:13           ` Sandy Harris
2001-08-12  8:00           ` David S. Miller
     [not found] <no.id>
2001-08-12 11:49 ` Alan Cox
2001-08-13 13:51 ` David S. Miller
2001-08-13 14:09 ` Alan Cox
2001-08-13 14:21 ` David S. Miller
2001-08-13 19:07   ` Gérard Roudier
2001-08-13 19:42   ` David S. Miller
2001-08-13 15:10 ` Alan Cox

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=20010811175626.O19169@athlon.random \
    --to=andrea@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@redhat.com \
    --cc=johannes@erdfelt.com \
    --cc=linux-kernel@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).