From: Andi Kleen <ak@suse.de>
To: Alan Cox <alan@redhat.com>
Cc: 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: Mon, 26 Jun 2006 08:24:45 +0200 [thread overview]
Message-ID: <200606260824.45506.ak@suse.de> (raw)
In-Reply-To: <20060625222115.GA17213@devserv.devel.redhat.com>
On Monday 26 June 2006 00:21, Alan Cox wrote:
> 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.
Should we hurt everybody for two terminally broken devices?
BCM4400 and its wireless brethen is fine with GFP_DMA btw and mostly only
exists in low end machines where most/all of the memory is below 2GB anyways
(so the check first approach works quite well)
>
> 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.
Blk-bounce would have the same effect.
If you set blk-bounce then the block layer will only bounce if the
address is < limit and it knows about the different zones on 32bit
and will use GFP_NORMAL there.
If you have upto 6GB you have a 50:50% chance of not bouncing at least.
The ifdef approach is just broken. Please fix it.
-Andi
next prev parent reply other threads:[~2006-06-26 6:24 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
2006-06-26 6:24 ` Andi Kleen [this message]
-- 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=200606260824.45506.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alan@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).