From: Dan Malek <dan@embeddededge.com>
To: Darin.Johnson@nokia.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: [RFC] consistent_sync and non L1 cache line aligned buffers
Date: Wed, 16 Jul 2003 10:01:38 -0400 [thread overview]
Message-ID: <3F155AC2.5000301@embeddededge.com> (raw)
In-Reply-To: F0B628F30F48064289D8CCC1EE21B7A80C48A8@mvebe001.americas.nokia.com
Darin.Johnson@nokia.com wrote:
> My headache example was the 4 byte buffer that MPC860 CPM
> was using to talk to an I2C device, there just wasn't an
> elegant solution...
You should have used consistent_alloc and never used consistent_sync()
in this case. FYI, consistent_sync() should never be used on
consistent_alloc()'ed buffers.....another tidbit for documentation.
The consistent_* are used to manage a variety of consistency related
features of non-coherent processors, not that you should necessarily
use all of them to solve a particular implementation requirement.
Thanks.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-16 14:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 23:04 [RFC] consistent_sync and non L1 cache line aligned buffers Darin.Johnson
2003-07-15 23:34 ` Paul Mackerras
2003-07-15 23:50 ` Eugene Surovegin
2003-07-15 23:45 ` Matt Porter
2003-07-16 14:01 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-16 0:12 Darin.Johnson
2003-07-15 20:47 Darin.Johnson
[not found] <F0B628F30F48064289D8CCC1EE21B7A80C48A5@mvebe001.americas.n okia.com>
2003-07-15 20:39 ` Eugene Surovegin
2003-07-15 21:26 ` David Blythe
2003-07-15 22:15 ` Dan Malek
2003-07-15 20:18 Darin.Johnson
2003-07-15 4:32 Eugene Surovegin
2003-07-15 15:46 ` Tom Rini
2003-07-15 16:20 ` Eugene Surovegin
2003-07-15 16:25 ` Tom Rini
2003-07-15 16:17 ` Matt Porter
2003-07-15 16:27 ` Eugene Surovegin
2003-07-15 23:51 ` Matt Porter
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=3F155AC2.5000301@embeddededge.com \
--to=dan@embeddededge.com \
--cc=Darin.Johnson@nokia.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).