From: Nye Liu <nyet@zumanetworks.com>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: Troy Benjegerdes <hozer@drgw.net>,
Michael Sokolov <msokolov@ivan.Harhan.ORG>,
linux-galileo@source.mvista.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: [Linux-galileo] Re: EV-64260-BP & GT64260 bi_recs
Date: Thu, 21 Mar 2002 14:10:31 -0800 [thread overview]
Message-ID: <20020321221031.GA6671@zumanetworks.com> (raw)
In-Reply-To: <3C9A301A.5B1B14DE@mvista.com>
On Thu, Mar 21, 2002 at 02:10:18PM -0500, Mark A. Greer wrote:
> Troy Benjegerdes wrote:
>
> > FYI, the gt eth driver is completely busticated for SMP. I managed to get
> > zuma's mpsc driver working on SMP by turning on snooping. (this may be the
> > 'wrong' thing to do , but it works for now)
>
> I haven't looked at the zuma version of the drivers but the ones inherited from
> marvell need to be dumped and completely rewritten...and made SMP-safe. Its been
> on my list but I haven't gotten around to do that. If/when I do, I'll look at what
> Nye, et. al. has done first. They may have all the issues settled already.
Mark: myself, Troy, and rex will be working on this. The serial driver
is fine in SMP (although it depends on snooping, which, according to
Galileo, is broken for SDMA *and* ETHDMA).
The GT's ethernet snooping is DEFINITELY broken; not sure where we will
go from here for smp. I will let people smarter than me handle that..
The good news is that PCI snooping seems to be rock solid.
Troy: the question in my mind is whether the SDMA snooping is always
safe or not. We will torture test the SDMA some here; but keep in mind
when we first did this, the SDMA snooping seems to cause problems
under severe stress testing, which is why by default the driver does
explicit cache flushes. Maybe things have changed since then; it needs
testing.
What I dont get is that in BOTH (SDMA and ETHDMA) situations (with
CPU snooping on), if DMA snooping is off, invalidates were still
required. Perhaps somebody more knowledgeable can explain why this is.
Mike S: I would also be VERY interested in any work you may have already
done in the mpsc or eth drivers; especially with regards to SMP and
cache coherency.
Finally, my EVB board is growing increasingly less stable by the day (i
think my cpu module is very loose; if i touch the cpu, the board bombs
out), so testing on that platform is becoming increasingly difficult.
The good news is that our custom board is pretty stable, but i would
still like other GT EVB users lurking here to stress test the _galileo
tree as best they can, since right now, I seem to be the only active
developer with an EVB contributing to _gal.
--
Nye Liu
nyet@zumanetworks.com
"Who would be stupid enough to quote a fictitious character?"
-- Don Quixote
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-03-21 22:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-20 1:02 EV-64260-BP & GT64260 bi_recs Michael Sokolov
2002-03-21 20:15 ` [Linux-galileo] " Troy Benjegerdes
2002-03-21 19:10 ` Mark A. Greer
2002-03-21 22:10 ` Nye Liu [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-20 17:04 Michael Sokolov
2002-03-21 20:36 ` Troy Benjegerdes
2002-03-21 19:17 ` Mark A. Greer
2002-03-21 21:36 ` Jim Potter
2002-03-21 22:15 ` [Linux-galileo] " Nye Liu
2002-03-21 20:19 ` Mark A. Greer
2002-03-25 4:19 Michael Sokolov
2002-03-25 11:10 ` Nye Liu
2002-03-25 4:31 Michael Sokolov
2002-03-25 6:30 ` Murray Jensen
2002-03-25 6:47 Michael Sokolov
2002-03-25 7:44 ` Murray Jensen
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=20020321221031.GA6671@zumanetworks.com \
--to=nyet@zumanetworks.com \
--cc=hozer@drgw.net \
--cc=linux-galileo@source.mvista.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mgreer@mvista.com \
--cc=msokolov@ivan.Harhan.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).