From: David Brownell <david-b@pacbell.net>
To: linux-usb-devel@lists.sourceforge.net,
Russell King <rmk@arm.linux.org.uk>
Cc: Manfred Spraul <manfred@colorfullife.com>,
zaitcev@redhat.com, linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: SLAB vs. pci_alloc_xxx in usb-uhci patch
Date: Mon, 05 Mar 2001 18:29:27 -0800 [thread overview]
Message-ID: <026b01c0a5e5$4513e740$6800000a@brownell.org> (raw)
In-Reply-To: <E14a6uW-0008Gd-00@the-village.bc.nu>
> > At the time, I didn't feel like creating a custom sub-allocator just
> > for USB, ...
> >
> > I'd be good to get it done "properly" at some point though.
>
> Something like
>
> struct pci_pool *pci_alloc_consistent_pool(int objectsize, int align)
struct pci_pool *
pci_create_consistent_pool (struct pci_dev *dev, int size, int align)
and similar for freeing the pool ... pci_alloc_consistent() needs the device,
presumably since some devices may need to dma into specific memory.
I'd probably want at least "flags" from kmem_cache_create().
> pci_alloc_pool_consistent(pool,..
> pci_free_pool_consistent(pool,..
These should have signatures just like pci_alloc_consistent() and
pci_free_consistent() except they take the pci_pool, not a pci_dev.
Oh, and likely GFP_ flags to control blocking.
> Where the pool allocator does page grabbing and chaining
Given an agreement on API, I suspect Johannes' patch could get
quickly generalized. Then debugging support (like in slab.c) could
be added later.
- Dave
next prev parent reply other threads:[~2001-03-07 6:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3AA91B2C.BEB85D8C@colorfullife.com>
2001-03-05 22:08 ` Manfred Spraul
2001-03-05 22:52 ` David Brownell
2001-03-05 23:20 ` Russell King
2001-03-06 2:09 ` Alan Cox
2001-03-06 2:29 ` David Brownell [this message]
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
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 21:38 ` [linux-usb-devel] " Alan Cox
2001-03-09 20:00 ` David S. Miller
2001-03-09 20:07 ` David S. Miller
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='026b01c0a5e5$4513e740$6800000a@brownell.org' \
--to=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=manfred@colorfullife.com \
--cc=rmk@arm.linux.org.uk \
--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
all inboxes | Powered by JetHome®