From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Richard Henderson <rth@twiddle.net>, linux-kernel@vger.kernel.org
Subject: Re: alpha iommu fixes
Date: Sun, 20 May 2001 16:12:34 +0400 [thread overview]
Message-ID: <20010520161234.B8223@jurassic.park.msu.ru> (raw)
In-Reply-To: <20010518214617.A701@jurassic.park.msu.ru> <20010519155502.A16482@athlon.random> <20010519231131.A2840@jurassic.park.msu.ru> <20010520044013.A18119@athlon.random>
In-Reply-To: <20010520044013.A18119@athlon.random>; from andrea@suse.de on Sun, May 20, 2001 at 04:40:13AM +0200
On Sun, May 20, 2001 at 04:40:13AM +0200, Andrea Arcangeli wrote:
> I was only talking about when you get the "pci_map_sg failed" because
> you have not 3 but 300 scsi disks connected to your system and you are
> writing to all them at the same time allocating zillons of pte, and one
> of your drivers (possibly not even a storage driver) is actually not
> checking the reval of the pci_map_* functions. You don't need a pte
> memleak to trigger it, even regardless of the fact I grown the dynamic
> window to 1G which makes it 8 times harder to trigger than in mainline.
I think you're too pessimistic. Don't mix "disks" and "controllers" --
SCSI adapter with 10 drives attached is a single DMA agent, not 10 agents.
If you're so concerned about Big Iron, go ahead and implement 64-bit PCI
support, it would be right long-term solution. I'm pretty sure that
high-end servers use mostly this kind of hardware.
Oh, well. This doesn't mean that I'm disagreed with what you said. :-)
Driver writers must realize that pci mappings are limited resources.
Ivan.
next prev parent reply other threads:[~2001-05-20 12:13 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-18 17:46 Ivan Kokshaysky
2001-05-19 2:34 ` Tom Vier
2001-05-19 10:48 ` Ivan Kokshaysky
2001-05-19 20:58 ` Tom Vier
2001-05-19 13:55 ` Andrea Arcangeli
2001-05-19 19:11 ` Ivan Kokshaysky
2001-05-20 2:40 ` Andrea Arcangeli
2001-05-20 12:12 ` Ivan Kokshaysky [this message]
2001-05-20 13:40 ` Andrea Arcangeli
2001-05-20 14:23 ` Gérard Roudier
[not found] ` <3B07AF49.5A85205F@uow.edu.au>
2001-05-20 13:49 ` Andrea Arcangeli
2001-05-20 14:05 ` Andrew Morton
2001-05-20 14:33 ` Andrea Arcangeli
2001-05-21 1:01 ` David S. Miller
2001-05-21 1:47 ` Andrea Arcangeli
2001-05-21 7:05 ` David S. Miller
2001-05-21 8:59 ` Andrea Arcangeli
2001-05-21 9:50 ` Gerd Knorr
2001-05-21 9:02 ` David S. Miller
2001-05-21 9:23 ` Andi Kleen
2001-05-21 9:30 ` David S. Miller
2001-05-21 9:42 ` Andi Kleen
2001-05-21 10:02 ` Andrea Arcangeli
2001-05-21 10:17 ` Alan Cox
2001-05-21 10:00 ` David S. Miller
2001-05-21 10:27 ` Andi Kleen
2001-05-21 22:22 ` Jens Axboe
2001-05-21 10:34 ` David S. Miller
2001-05-21 10:42 ` Andi Kleen
2001-05-21 10:55 ` David S. Miller
2001-05-21 11:08 ` Andi Kleen
2001-05-21 11:36 ` David S. Miller
2001-05-21 11:41 ` Andi Kleen
2001-05-21 9:56 ` Andrea Arcangeli
2001-05-21 10:19 ` David S. Miller
2001-05-21 11:00 ` Andrea Arcangeli
2001-05-21 11:04 ` David S. Miller
2001-05-21 11:27 ` Andrea Arcangeli
2001-05-21 12:16 ` Peter Rival
2001-05-22 11:12 ` Chris Wedgwood
2001-05-22 17:51 ` Jonathan Lundell
2001-05-21 10:11 ` David S. Miller
2001-05-21 10:50 ` Andrea Arcangeli
2001-05-21 10:59 ` David S. Miller
2001-05-21 11:19 ` Andrea Arcangeli
2001-05-21 11:51 ` Ivan Kokshaysky
2001-05-21 17:53 ` Richard Henderson
2001-05-22 0:56 ` Andrea Arcangeli
2001-05-22 14:29 ` Andrea Arcangeli
2001-05-22 14:44 ` Ivan Kokshaysky
2001-05-22 15:00 ` Andrea Arcangeli
2001-05-22 20:28 ` Richard Henderson
2001-05-22 20:40 ` Jeff Garzik
2001-05-22 20:52 ` Andrea Arcangeli
2001-05-22 20:57 ` Richard Henderson
2001-05-22 21:09 ` Alan Cox
2001-05-22 21:08 ` Alan Cox
2001-05-22 20:48 ` Jonathan Lundell
2001-05-22 21:02 ` Richard Henderson
2001-05-22 21:10 ` Alan Cox
2001-05-22 21:17 ` Jonathan Lundell
2001-05-22 21:24 ` Alan Cox
2001-05-22 21:34 ` Jonathan Lundell
2001-05-22 15:18 ` Andrea Arcangeli
2001-05-22 15:55 ` Ivan Kokshaysky
2001-05-22 16:06 ` Andrea Arcangeli
2001-05-22 13:22 ` Andrea Arcangeli
2001-05-21 13:55 ` Jonathan Lundell
2001-05-21 14:17 ` Ivan Kokshaysky
2001-05-21 15:47 ` Jonathan Lundell
2001-05-20 16:18 ` Andrea Arcangeli
2001-05-20 16:21 ` Andrew Morton
2001-05-20 16:44 ` Andrea Arcangeli
2001-05-20 16:54 ` Andrew Morton
2001-05-20 17:12 ` Andrea Arcangeli
2001-05-21 1:07 ` David S. Miller
2001-05-21 1:37 ` Andrea Arcangeli
2001-05-21 6:53 ` David S. Miller
2001-05-21 7:59 ` Alan Cox
2001-05-21 8:06 ` Chris Wedgwood
2001-05-21 8:09 ` David S. Miller
2001-05-21 8:09 ` Alan Cox
2001-05-23 0:05 ` Albert D. Cahalan
2001-05-22 13:11 ` Pavel Machek
2001-05-22 23:02 ` David S. Miller
2001-05-20 17:16 ` Jeff Garzik
2001-05-20 17:37 ` Andrea Arcangeli
2001-05-21 1:00 ` David S. Miller
2001-05-21 7:47 ` Alan Cox
2001-05-21 7:53 ` David S. Miller
2001-05-21 8:03 ` Alan Cox
2001-05-21 8:11 ` David S. Miller
2001-05-21 1:03 ` David S. Miller
2001-05-21 1:58 ` Richard Henderson
2001-05-20 1:11 ` Richard Henderson
2001-05-20 12:05 ` Ivan Kokshaysky
2001-05-21 0:37 ` Richard Henderson
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=20010520161234.B8223@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
/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
all inboxes | Powered by JetHome®