From: erik quanstrom <quanstro@quanstro.net>
To: charles.forsyth@gmail.com, 9fans@9fans.net
Subject: Re: [9fans] sheevaplug SD card driver
Date: Fri, 19 Oct 2012 17:49:51 -0400 [thread overview]
Message-ID: <ee240a7b3684b583af2d12605eeceb83@brasstown.quanstro.net> (raw)
In-Reply-To: <CAOw7k5hmGSjMOp+N1H4zFBsSF=zMj=G7iAmJeV79FV=xtga9RA@mail.gmail.com>
On Fri Oct 19 17:31:50 EDT 2012, charles.forsyth@gmail.com wrote:
> I think it's better to specify memory that must have special cache
> properties, rather than assuming that everything is.
this depends on the ratio of memory that has special cache
properties to the memory that doesn't. if you have devices
like the kirkwood that can do dma, pci transfers, crcs, etc and
it turns out that you can't predict ahead of time what memory
you'd like to transfer, then, making a small concession in
malloc might make sense. Block*s (well at least the buffer)
needs to be special because the ethernet on the marvell is not
cache coherent.
- erik
next prev parent reply other threads:[~2012-10-19 21:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 12:42 Richard Miller
2012-10-18 13:46 ` Gorka Guardiola
2012-10-18 14:24 ` David du Colombier
2012-10-19 13:36 ` Richard Miller
2012-10-19 13:47 ` erik quanstrom
2012-10-19 14:00 ` Richard Miller
2012-10-19 15:30 ` erik quanstrom
2012-10-19 15:39 ` Richard Miller
2012-10-19 15:46 ` erik quanstrom
2012-10-19 16:03 ` Richard Miller
2012-10-19 21:30 ` Charles Forsyth
2012-10-19 21:49 ` erik quanstrom [this message]
2012-10-19 21:59 ` Charles Forsyth
2012-11-10 12:20 ` Richard Miller
2012-10-18 16:05 ` Skip Tavakkolian
2012-10-19 15:21 lucio
2012-10-19 15:33 ` Richard Miller
2012-10-19 16:01 ` lucio
2012-10-19 15:39 ` Skip Tavakkolian
2012-11-10 13:24 Erik Quanstrom
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=ee240a7b3684b583af2d12605eeceb83@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=charles.forsyth@gmail.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;
as well as URLs for NNTP newsgroup(s).