From: Russell King <rmk@arm.linux.org.uk>
To: manfred@colorfullife.com (Manfred Spraul)
Cc: johannes@erdfelt.com (Johannes Erdfelt), linux-kernel@vger.kernel.org
Subject: Re: Inefficient PCI DMA usage (was: [experimental patch] UHCI updates)
Date: Sun, 21 Jan 2001 10:51:15 +0000 (GMT) [thread overview]
Message-ID: <200101211051.f0LApFv02203@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3A6A9F9A.3CDE1B05@colorfullife.com> from "Manfred Spraul" at Jan 21, 2001 09:36:42 AM
Manfred Spraul writes:
> Not yet, but that would be a 2 line patch (currently it's hardcoded to
> BYTES_PER_WORD align or L1_CACHE_BYTES, depending on the HWCACHE_ALIGN
> flag).
I don't think there's a problem then. However, if slab can be told "I want
1024 bytes aligned to 1024 bytes" then I can get rid of
arch/arm/mm/small_page.c (separate problem to the one we're discussing
though) ;)
> But there are 2 other problems:
> * kmem_cache_alloc returns one pointer, pci_alloc_consistent 2 pointers:
> one dma address, one virtual address.
> * The code relies on the virt_to_page() macro.
What I'm wondering is what about a wrapper around the slab allocator, in
a similar way to pci_alloc_consistent() is a wrapper around gfp. Since
the slab allocator returns "pointers" in the same space as gfp returns
page references, there shouldn't be a problem (Linus may complain here).
ie, we could make pci_alloc_consistent() a little more intelligent and
allocate from the slab for small sizes, but use gfp for larger sizes?
Comments, anyone (DaveM, Linus, et al) ?
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King rmk@arm.linux.org.uk --- ---
| | | | http://www.arm.linux.org.uk/personal/aboutme.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
-
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 10:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-20 18:00 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 [this message]
2001-01-21 11:49 ` Manfred Spraul
2001-01-21 17:37 ` Johannes Erdfelt
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=200101211051.f0LApFv02203@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=johannes@erdfelt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/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