From: Johannes Erdfelt <johannes@erdfelt.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Manfred Spraul <manfred@colorfullife.com>, linux-kernel@vger.kernel.org
Subject: Re: Inefficient PCI DMA usage (was: [experimental patch] UHCI updates)
Date: Sun, 21 Jan 2001 12:37:31 -0500 [thread overview]
Message-ID: <20010121123730.N9156@sventech.com> (raw)
In-Reply-To: <20010120130848.I9156@sventech.com> <200101202315.f0KNFTV01790@flint.arm.linux.org.uk>
In-Reply-To: <200101202315.f0KNFTV01790@flint.arm.linux.org.uk>; from Russell King on Sat, Jan 20, 2001 at 11:15:28PM +0000
On Sat, Jan 20, 2001, Russell King <rmk@arm.linux.org.uk> wrote:
> Johannes Erdfelt writes:
> > They need to be visible via DMA. They need to be 16 byte aligned. We
> > also have QH's which have similar requirements, but we don't use as many
> > of them.
>
> Can we get away from the "16 byte aligned" and make it "n byte aligned"?
> I believe that slab already has support for this?
If you look at the part of the message that I quoted and you cut off,
the requirements for UHCI are the data structures MUST be 16 byte aligned.
I don't mind if the API is more generalized, but those are the
requirements that were asked about in this specific case.
JE
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-21 17:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-20 18:00 Inefficient PCI DMA usage (was: [experimental patch] UHCI updates) Manfred Spraul
2001-01-20 18:08 ` Johannes Erdfelt
2001-01-20 23:15 ` Russell King
2001-01-21 8:36 ` Manfred Spraul
2001-01-21 10:51 ` Russell King
2001-01-21 11:49 ` Manfred Spraul
2001-01-21 17:37 ` Johannes Erdfelt [this message]
2001-01-21 23:11 ` Russell King
[not found] <3A691043.F18CA6CA@megapathdsl.net>
2001-01-20 5:38 ` Johannes Erdfelt
2001-01-20 8:28 ` Russell King
2001-01-20 17:34 ` Johannes Erdfelt
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=20010121123730.N9156@sventech.com \
--to=johannes@erdfelt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=rmk@arm.linux.org.uk \
/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.