From: Russell King <rmk@arm.linux.org.uk>
To: David Brownell <david-b@pacbell.net>
Cc: Manfred Spraul <manfred@colorfullife.com>,
zaitcev@redhat.com, linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: SLAB vs. pci_alloc_xxx in usb-uhci patch
Date: Mon, 5 Mar 2001 23:20:53 +0000 [thread overview]
Message-ID: <20010305232053.A16634@flint.arm.linux.org.uk> (raw)
In-Reply-To: <001f01c0a5c0$e942d8f0$5517fea9@local> <00d401c0a5c6$f289d200$6800000a@brownell.org>
In-Reply-To: <00d401c0a5c6$f289d200$6800000a@brownell.org>; from david-b@pacbell.net on Mon, Mar 05, 2001 at 02:52:24PM -0800
On Mon, Mar 05, 2001 at 02:52:24PM -0800, David Brownell wrote:
> I didn't see that thread. I agree, pci_alloc_consistent() already has
> a signature that's up to the job. The change you suggest would need
> to affect every architecture's implementation of that code ... which
> somehow seems not the best solution at this time.
Needless to say that USB is currently broken for the architectures that
need pci_alloc_consistent.
A while ago, I looked at what was required to convert the OHCI driver
to pci_alloc_consistent, and it turns out that the current interface is
highly sub-optimal. It looks good on the face of it, but it _really_
does need sub-page allocations to make sense for USB.
At the time, I didn't feel like creating a custom sub-allocator just
for USB, and since then I haven't had the inclination nor motivation
to go back to trying to get my USB mouse or iPAQ communicating via USB.
(I've not used this USB port for 3 years anyway).
I'd be good to get it done "properly" at some point though.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-03-05 23:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-05 22:08 SLAB vs. pci_alloc_xxx in usb-uhci patch Manfred Spraul
2001-03-05 22:52 ` David Brownell
2001-03-05 23:20 ` Russell King [this message]
2001-03-06 2:09 ` Alan Cox
2001-03-06 2:29 ` [linux-usb-devel] " David Brownell
2001-03-06 4:53 ` David S. Miller
2001-03-09 16:18 ` SLAB vs. pci_alloc_xxx in usb-uhci patch [RFC: API] David Brownell
[not found] ` <3AA91B2C.BEB85D8C@colorfullife.com>
2001-03-09 18:21 ` David S. Miller
2001-03-09 18:35 ` [linux-usb-devel] " Johannes Erdfelt
2001-03-09 19:42 ` David Brownell
2001-03-09 20:07 ` David S. Miller
2001-03-09 21:14 ` David Brownell
2001-03-09 22:34 ` Pete Zaitcev
2001-03-09 18:35 ` Alan Cox
2001-03-09 18:29 ` David Brownell
2001-03-09 19:14 ` Pete Zaitcev
2001-03-09 19:37 ` David Brownell
2001-03-09 19:04 ` Gérard Roudier
2001-03-09 22:42 ` David Brownell
2001-03-09 21:07 ` Gérard Roudier
2001-03-10 3:11 ` David Brownell
2001-03-09 20:00 ` David S. Miller
2001-03-09 21:38 ` [linux-usb-devel] " Alan Cox
2001-03-09 20:07 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2001-03-06 5:44 SLAB vs. pci_alloc_xxx in usb-uhci patch Peter Zaitcev
2001-03-06 23:13 ` David Brownell
2001-03-07 7:05 ` Manfred Spraul
2001-03-07 17:43 ` David Brownell
2001-03-05 19:23 Peter Zaitcev
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=20010305232053.A16634@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=manfred@colorfullife.com \
--cc=zaitcev@redhat.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