From: Martin Wilck <Martin.Wilck@fujitsu-siemens.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] IO/TLB bounce buffer space
Date: Tue, 12 Jun 2001 08:44:12 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005716@msgid-missing> (raw)
Hi,
it is becoming apparent that the limited bounce buffer space is the reason
for the crashes with the new aic7xxx driver and linux-IA64 with >=4GB RAM
that I reported previously.
If I understand it right,
the driver uses up to 253 buffers per device, each of which can be 8kB in
size. Consequently, it almost completely fills up the available IO/TLB
space.
Question: Would it hurt to increase IO/TLB space on machines with large
memory? Would it be possible and make sense to make IO/TLB space size a
kernel configuration option?
Regards,
Martin
--
Martin Wilck <Martin.Wilck@fujitsu-siemens.com>
FSC EP PS DS1, Paderborn Tel. +49 5251 8 15113
next reply other threads:[~2001-06-12 8:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 8:44 Martin Wilck [this message]
2001-06-12 16:23 ` [Linux-ia64] IO/TLB bounce buffer space root
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-105590693005716@msgid-missing \
--to=martin.wilck@fujitsu-siemens.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