From: Larry Finger <Larry.Finger@lwfinger.net>
To: LKML <linux-kernel@vger.kernel.org>
Subject: DMA descriptor alignment
Date: Mon, 12 Nov 2007 00:15:56 -0600 [thread overview]
Message-ID: <4737EF9C.4010207@lwfinger.net> (raw)
For those variants of BCM43xx cards that use 64-bit DMA, there is a requirement that all descriptor
rings must be aligned on an 8K boundary and must fit within an 8K page. On the x86_64 architecture
where the page size is 4K, I was getting addresses like 0x67AF000 when using dma_alloc_coherent
calls. From the description of the dma_pool_create and dma_pool_allocate routines, I thought they
would fix my problems; however, even with a dma_pool_create(name, dev, 8192, 8192, 8192) call, I'm
still getting 4K rather than 8K alignment, which results in DMA errors.
Is there a bug in these routines, am I using them incorrectly, or do I have a misunderstanding of
what it takes to get this kind of alignment?
Thanks,
Larry
next reply other threads:[~2007-11-12 6:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 6:15 Larry Finger [this message]
2007-11-13 17:00 ` DMA descriptor alignment Andi Kleen
2007-11-14 14:41 ` Larry Finger
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=4737EF9C.4010207@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-kernel@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