From: Ralph Blach <rblach@intrex.net>
To: Dan Malek <dan@mvista.com>
Cc: frowand@mvista.com, linuxppc-embedded@lists.linuxppc.org,
David Blythe <blythe@routefree.com>
Subject: Re: Proposed new kernel noncaching memory allocator for the 405gp
Date: Thu, 22 Mar 2001 17:18:15 -0500 [thread overview]
Message-ID: <3ABA7A27.B4CC8355@intrex.net> (raw)
In-Reply-To: 3ABA6D60.46D844F3@mvista.com
Dan,
No, the transmit descriptors in the USB code are much less than a page. Look
at ohci-usb.c
Why do a kmalloc? And what about SCSI and it linked list? These need bytes and
not whole pages.
Any I'll do it and submitt it .
Chip
Dan Malek wrote:
> Ralph Blach wrote:
>
> > Yes, but these allocate on a page boundry and I was thinking of something a
> > little more granular.
>
> You can only control cache behavior on page boundaries at best, and
> from the few drivers I have looked at, this is exactly what they
> expect.
>
> > Any objections?
>
> I have been listing them in previous messages.
>
> -- Dan
--
Ralph "Chip" Blach
KF4WBK
Chapel Hill, North Carolina
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-03-22 22:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 15:34 Proposed new kernel noncaching memory allocator for the 405gp Ralph Blach
2001-03-22 16:32 ` 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 [this message]
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=3ABA7A27.B4CC8355@intrex.net \
--to=rblach@intrex.net \
--cc=blythe@routefree.com \
--cc=dan@mvista.com \
--cc=frowand@mvista.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).