From: Martin Wilck <Martin.Wilck@fujitsu-siemens.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] IO/TLB bounce buffer space
Date: Mon, 25 Jun 2001 11:37:43 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005754@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005716@msgid-missing>
Dear Rich, all,
> In my experience, the question of the peak demand a system may
> experience must be governed by
> 1. what you, the supplier, spec as the peak demand it supports,
> 2. what the customer understands is the max load the system
> can be utilized to perform, and have paid to obtain.
> 3. and any shortfall in actual delivered performance from your spec
> you can be sure the customer will demand you the supplier pay
> to make up the difference!
>
> This leaves no room for statistical analysis! The customer will not
> view that using all the resources at once is unlikely and not expected.
> If you spec 4 controllers of 32 devices each of 253 buffers needed for
> their peak operation, then the system better deliver this.
> Or you should change your spec and reduce the numbers.
I completely agree with you. I just didn't want to sound too harsh in my
analysis of the problem (the harsh version is: This controller/driver
combination is not suitable for production systems on IA/64).
Justing Gibbs is implementing 39bit addressing into the aix7xxx
driver right now. Once finished, this will solve the problem.
Regards,
Martin
--
Martin Wilck <Martin.Wilck@fujitsu-siemens.com>
FSC EP PS DS1, Paderborn Tel. +49 5251 8 15113
next prev parent reply other threads:[~2001-06-25 11:37 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
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 [this message]
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-105590693005754@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.