From: Ralph Blach <rblach@intrex.net>
To: linuxppc-embedded@lists.linuxppc.org,
David Blythe <blythe@routefree.com>
Subject: Proposed new kernel noncaching memory allocator for the 405gp
Date: Thu, 22 Mar 2001 10:34:03 -0500 [thread overview]
Message-ID: <3ABA1B6A.87C5FE9B@intrex.net> (raw)
David,
This is what I propose,
I propose a kmalloc_noncache and a kfree_noncached.
These would be module and would be loaded when necessary. They would
operate allocating say 16k (could be any size) of memory during boot
time
and then mapping it non cached. The the kmalloc_noncached routine would
carve out little chucks of it and the free routine would release it. It
would also have a noncached to real routine
to return the real address of a noncached section.
Does this sound interesting?
Chip
David Blythe wrote:
> Ralph Blach wrote:
> >
> > David,
> >
> > Do you have USB working from on OHCI pci card?
> >
> > Would a kmalloc_nocache and kfree_cache be useful to you?
> >
> > Chip
> >
> >
>
> I think something more general then pci_alloc_consistent would be
better
> for devices that are not pci based. We are still working on getting a
> pci OHCI usb to work with the walnut card and are running into a lot
of
> cache coherency problems.
> david
--
Ralph "Chip" Blach
KF4WBK
Chapel Hill, North Carolina
--
Ralph "Chip" Blach
KF4WBK
Chapel Hill, North Carolina
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-03-22 15:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 15:34 Ralph Blach [this message]
2001-03-22 16:32 ` Proposed new kernel noncaching memory allocator for the 405gp Dan Malek
2001-03-22 17:46 ` Ralph Blach
2001-03-22 18:27 ` Dan Malek
2001-03-23 14:14 ` Kernel Dumps Brad Bonkoski
2001-03-23 15:10 ` Wolfgang Denk
2001-03-22 19:24 ` Proposed new kernel noncaching memory allocator for the 405gp Frank Rowand
2001-03-22 19:50 ` Dan Malek
2001-03-22 20:57 ` Ralph Blach
2001-03-22 21:14 ` Frank Rowand
2001-03-22 21:23 ` Dan Malek
2001-03-22 22:06 ` acmay
2001-03-22 22:18 ` Ralph Blach
2001-03-25 1:42 ` Brad Parker
2001-03-22 23:04 ` andrew may
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=3ABA1B6A.87C5FE9B@intrex.net \
--to=rblach@intrex.net \
--cc=blythe@routefree.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).