From: Larry Finger <Larry.Finger@lwfinger.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: "John W. Linville" <linville@tuxdriver.com>,
bcm43xx-dev@lists.berlios.de,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] b43: Enforce DMA descriptor memory constraints
Date: Wed, 18 Nov 2009 14:31:14 -0600 [thread overview]
Message-ID: <4B045992.6070600@lwfinger.net> (raw)
In-Reply-To: <200911182053.05488.mb@bu3sch.de>
On 11/18/2009 01:53 PM, Michael Buesch wrote:
> Enforce all device constraints on the descriptor memory region.
>
> There are several constraints on the descriptor memory, as documented
> in the specification. The current code does not enforce them and/or
> incorrectly enforces them.
>
> Those constraints are:
> - The address limitations on 30/32bit engines, that also apply to
> the skbs.
> - The 4k alignment requirement on 30/32bit engines.
> - The 8k alignment requirement on 64bit engines.
>
> Signed-off-by: Michael Buesch <mb@bu3sch.de>
>
> ---
>
> It's not entirely clear if any 64bit devices exist that _really_ need the 8k
> alignment. However, I think it does not hurt much if we enforce it anyway.
> The patch removes the always-set-GFP_DMA-on-64bit-devices hack. The combination of
> the new enforcements should be enough to keep every device happy, including those
> which needed the GFP_DMA hack. The new code will dynamically check if GFP_DMA is
> required, instead of statically doing it all the time.
> John, please queue for the next feature release. This patch still needs a fair
> amount of testing. I think the best way to get it is to simply apply it. If this
> causes any regressions, we can (temporary) revert it.
>
> This also is a candidate for a b43legacy backport.
Tested OK for BCM4312 (14e4:4315).
I will port/test on b43legacy as I have the hardware.
Larry
prev parent reply other threads:[~2009-11-18 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 19:53 [PATCH] b43: Enforce DMA descriptor memory constraints Michael Buesch
2009-11-18 20:31 ` Larry Finger [this message]
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=4B045992.6070600@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
/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.