mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: benh@kernel.crashing.org
Cc: benoit.boissinot@ens-lyon.org, mb@bu3sch.de,
	netdev@vger.kernel.org, bcm43xx-dev@lists.berlios.de,
	linux-kernel@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [RFC/PATCH] remove unneeded check in bcm43xx
Date: Tue, 11 Apr 2006 14:34:07 -0700 (PDT)	[thread overview]
Message-ID: <20060411.143407.74615246.davem@davemloft.net> (raw)
In-Reply-To: <1144788541.19353.41.camel@localhost.localdomain>

From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: Wed, 12 Apr 2006 06:49:00 +1000

> I would tend to agree... except that the broadcom is _the_ wireless
> card shipped by Apple with all of their machines for the last few
> years, and thus, the problem will be hit by pretty much any G5 user
> trying to use theirs...
>
> I don't have another idea on how to fix that at hand... a dma mask
> limit in the iommu layer is fairly easy to implement with our iommu
> implementation (though it wouldn't work on pseries where ranges are
> allocated per slot, but it would work fine on a g5). Still sounds
> better than introducing a ZONE_DMA separate from ZONE_NORMAL ...

I still think we shouldn't reward shit hardware by complicating
up our DMA mappings internals. :-)

If you're going to do it anyways, we use a nearly identical
allocation bitmap algorithm under sparc64 so maybe you can
take a stab at trying to put your code there too.  I'm more
than happy to test and integrate.

Thanks.

  reply	other threads:[~2006-04-11 21:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-10  4:01 Benoit Boissinot
     [not found] ` <200604100607.33362.mb@bu3sch.de>
2006-04-10  4:22   ` Benoit Boissinot
     [not found]     ` <200604100628.01483.mb@bu3sch.de>
2006-04-10  4:38       ` Benoit Boissinot
2006-04-10 13:46       ` John W. Linville
2006-04-10 16:18         ` Arjan van de Ven
2006-04-10 22:13         ` Benoit Boissinot
2006-04-10 22:28           ` David S. Miller
2006-04-11  1:47           ` Benjamin Herrenschmidt
2006-04-11  1:46     ` Benjamin Herrenschmidt
     [not found]       ` <200604110353.52067.mb@bu3sch.de>
2006-04-11  2:23         ` Benoit Boissinot
2006-04-11  5:49       ` David S. Miller
2006-04-11 20:49         ` Benjamin Herrenschmidt
2006-04-11 21:34           ` David S. Miller [this message]
2006-04-11 22:20             ` Benjamin Herrenschmidt
2006-04-11 22:21             ` Benjamin Herrenschmidt
2006-04-11 22:30               ` Benoit Boissinot
2006-04-11 22:35                 ` Benjamin Herrenschmidt

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=20060411.143407.74615246.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=benh@kernel.crashing.org \
    --cc=benoit.boissinot@ens-lyon.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    --cc=netdev@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
Powered by JetHome