From: Alan Cox <alan@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: Alan Cox <alan@redhat.com>,
torvalds@osdl.org, discuss@x86-64.org, akpm@osdl.org,
markh@osdl.org, linux-scsi@vger.kernel.org, axboe@suse.de
Subject: Re: [PATCH] [29/82] x86_64: Rename IOMMU option, fix help and mark option embedded.
Date: Sun, 25 Jun 2006 18:21:15 -0400 [thread overview]
Message-ID: <20060625222115.GA17213@devserv.devel.redhat.com> (raw)
In-Reply-To: <200606252132.41121.ak@suse.de>
On Sun, Jun 25, 2006 at 09:32:41PM +0200, Andi Kleen wrote:
> > From a tiny 16MB DMA pool that can't sustain the required load ? Or has that
> > bit changed.
>
> It should be ok because it blocks. It will be slow, but what else do you expect
> from broken hardware like this?
Sustained 80Mbyte/second I/O rates. At least thats what it gets in other OS
products. This is one of the reasons (broadcomm 4400 was another) that a 30
or 31 bit DMA zone not a 32bit one was called for, which also didn't happen
it seems.
The ifdef approach isnt perfect but it essentially means you get good
performance on x86-32 and only x86-64 has problems which seems fine to me,
because its an old card.
Alan
next prev parent reply other threads:[~2006-06-25 22:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-24 0:19 [PATCH] [29/82] x86_64: Rename IOMMU option, fix help and mark option embedded Andi Kleen
2006-06-24 23:14 ` Alan Cox
2006-06-25 15:22 ` Andi Kleen
2006-06-25 19:00 ` Alan Cox
2006-06-25 19:32 ` Andi Kleen
2006-06-25 22:21 ` Alan Cox [this message]
2006-06-26 6:24 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2006-06-26 12:37 Salyzyn, Mark
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=20060625222115.GA17213@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-scsi@vger.kernel.org \
--cc=markh@osdl.org \
--cc=torvalds@osdl.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.