From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [RFC/PATCH] EMAC "powerpc" port
Date: Fri, 22 Dec 2006 15:13:37 +1100 [thread overview]
Message-ID: <1166760817.6673.90.camel@localhost.localdomain> (raw)
In-Reply-To: <1166595738.19254.140.camel@localhost.localdomain>
On Wed, 2006-12-20 at 17:22 +1100, Benjamin Herrenschmidt wrote:
> - Locking. Cell is SMP, 46x is SMP, so we need SMP (and I've heard some
> of the -rt folks having problem in that area too). I haven't triple
> checked what I've done, it's rather simplistic, so feel free to propose
> something better, and I still have a race with the multicast stuff that
> I need to fix, but the base idea is that "hard" work and PHY polling are
> all done at task level so we can use mutexes for most things (zmii,
> rgmii, mdio accesses, etc...) and no big latencies.
I've fixed the race with the multicast stuff and updated the patch, it's
now:
http://gate.crashing.org/~benh/powerpc-emac-new-20061222.diff
Note that porting to the generic PHY layer might be a problem due to the
locking done by it (it basically calls back the MDIO access routines
with locks held or from timer interrupts while I'm using mutexes to
handle arbitration at the MDIO and ZMII/RGMII level). I'm not trying to
change the generic PHY layer but that might take some time.
I've tested it a bit more, running all sorts of data overnight through
an SSH link (good to detect data corruption) and it held firm without
apparent race or memory leak, but it could certainly be tortured more.
I'll do that once I've added support for dma unmapping, so I can test it
with the cell iommu active, as using an iommu is a very good way to
catch problems like runaway DMA etc...
Ben.
prev parent reply other threads:[~2006-12-22 4:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 6:22 [RFC/PATCH] EMAC "powerpc" port Benjamin Herrenschmidt
2006-12-22 4:13 ` Benjamin Herrenschmidt [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=1166760817.6673.90.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.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).