From: root <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] IO/TLB bounce buffer space
Date: Tue, 12 Jun 2001 16:23:32 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005718@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005716@msgid-missing>
>>>>> On Tue, 12 Jun 2001 10:44:12 +0200 (CEST), Martin Wilck <Martin.Wilck@fujitsu-siemens.com> said:
Martin> it is becoming apparent that the limited bounce buffer space
Martin> is the reason for the crashes with the new aic7xxx driver
Martin> and linux-IA64 with >=4GB RAM that I reported previously.
Martin> If I understand it right, the driver uses up to 253 buffers
Martin> per device, each of which can be 8kB in size. Consequently,
Martin> it almost completely fills up the available IO/TLB space.
The deeper question is of course: is this really a good idea? From a
latency perspective, such long queues may not make a lot of sense.
Even from a throughput perspective the benefit of using a 253 entry
queue is probably negligible compared to a shorter queue. Reading
aic7xxx.h, I get the impression that the author chose 253 as the max
queue length because s/he could. I don't see anything that suggests
that this length is optimal in any sense. It might be worth
experimenting with.
Martin> Question: Would it hurt to increase IO/TLB space on machines
Martin> with large memory? Would it be possible and make sense to
Martin> make IO/TLB space size a kernel configuration option?
An alternative is to use GFP_ATOMIC allocation. I'm not sure that
counts as a "solution" though as it arguably just hides the real
issue.
--david
next prev parent reply other threads:[~2001-06-12 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 8:44 [Linux-ia64] IO/TLB bounce buffer space Martin Wilck
2001-06-12 16:23 ` root [this message]
2001-06-12 17:01 ` Martin Wilck
2001-06-12 17:52 ` root
2001-06-22 22:50 ` Rich Altmaier
2001-06-24 15:20 ` Rik van Riel
2001-06-25 11:37 ` Martin Wilck
2001-06-25 21:14 ` David Mosberger
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=marc-linux-ia64-105590693005718@msgid-missing \
--to=davidm@hpl.hp.com \
--cc=linux-ia64@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