From: Scott Wood <scottwood@freescale.com>
To: Joakim Tjernlund <Joakim.Tjernlund@transmode.se>
Cc: linuxppc-dev@ozlabs.org, Li Yang <leoli@freescale.com>,
pku.leo@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH] ucc_geth: Rework the TX logic.
Date: Tue, 31 Mar 2009 09:37:48 -0500 [thread overview]
Message-ID: <49D22ABC.5050408@freescale.com> (raw)
In-Reply-To: <OFEAA9D1E3.4B2F3270-ONC125758A.00307236-C125758A.00322239@transmode.se>
Joakim Tjernlund wrote:
> I am a bit confused, what isn't worth it?
Enabling cacheing on MURAM, at least when used for buffer descriptors.
The cache line ping-pong would probably outweigh the cost of the
uncached accesses.
> Currently MURAM isn't used by ucc_geth,
Hmm. I looked in the driver and saw numerous muram allocations, but I
didn't try to follow the driver enough to ensure that they were for the
ring. I'd assumed it was similar to the CPM1/CPM2 driver.
> 3) as gianfar, dma_alloc_coherent(). I presume this is uncacheable memory?
It would be uncacheable on systems without coherent DMA, but I don't
think there are any such systems that use gianfar.
> My guess would be 2 or 3. Do they have the same synchronization
> sematics?
No, unfortunately. PowerPC sync instructions are a bit complicated.
For example, you can use eieio to sync between reading the interrupt
status register and checking the ring buffer, if they're both mapped
I+G, but not if the former is I+G and the latter is cacheable (you need
a full sync in that case).
-Scott
next prev parent reply other threads:[~2009-03-31 14:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 17:44 [PATCH] ucc_geth: Rework the TX logic Joakim Tjernlund
2009-03-26 18:03 ` Anton Vorontsov
2009-03-26 18:26 ` Joakim Tjernlund
2009-03-27 9:45 ` Li Yang
2009-03-27 10:23 ` Joakim Tjernlund
2009-03-27 10:39 ` Li Yang
2009-03-27 11:39 ` Joakim Tjernlund
2009-03-27 13:26 ` Scott Wood
2009-03-30 16:38 ` Joakim Tjernlund
2009-03-30 17:22 ` Scott Wood
2009-03-30 17:34 ` Joakim Tjernlund
2009-03-30 17:45 ` Scott Wood
2009-03-30 18:42 ` Joakim Tjernlund
2009-03-30 19:32 ` Scott Wood
2009-03-31 9:07 ` Joakim Tjernlund
2009-03-31 10:58 ` Li Yang
2009-03-31 14:37 ` Scott Wood [this message]
2009-03-31 8:16 ` Li Yang
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=49D22ABC.5050408@freescale.com \
--to=scottwood@freescale.com \
--cc=Joakim.Tjernlund@transmode.se \
--cc=leoli@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=pku.leo@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).