linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Gurevich <vag@paulidav.org>
To: Donald White <dbwhite@asu.edu>
Cc: linux-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Question about porting VxWorks driver
Date: Thu, 03 Apr 2003 07:41:31 -0800	[thread overview]
Message-ID: <3E8C562B.5090709@paulidav.org> (raw)
In-Reply-To: 3E8BECA6.6060709@asu.edu


Hello Donald,

Is it one of Hifn chips by any chance? If yes, then I can
tell you that their drivers do not know about cache flushes
and invalidates at all, which presents a real challenge on
PowerPC.

Writeback cache usually won't work. You have to manually
flush it before sending a message to the board and invalidate
it after you receive the encrypted (decrypted) message back.
If you do the transformation "in-place" then you can use
flush-and-invalidate before seding the message. Using uncached
memory is another option, but if you want to do further
processing without copying data to a cached buffer, you
performance will likely suffer.

In general you keep data buffers in cached memory and
do manual flushes/invalidates when needed, but keep
buffer descriptors and other similar structures (as
well as chip's registers and chip's private memory)
in uncached space.

Best regards,
Vladimir


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      parent reply	other threads:[~2003-04-03 15:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-03  8:11 Question about porting VxWorks driver Donald White
2003-04-03 15:27 ` Dan Malek
2003-04-03 15:41 ` Vladimir Gurevich [this message]

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=3E8C562B.5090709@paulidav.org \
    --to=vag@paulidav.org \
    --cc=dbwhite@asu.edu \
    --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).