From: Benjamin Herrenschmidt <bh40@calva.net>
To: Mark Knecht <mknecht@controlnet.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: [Linux1394-devel] Re: FireWire + Apple PB G3: some success
Date: Thu, 24 Feb 2000 20:21:31 +0100 [thread overview]
Message-ID: <20000224202131.012502@mailhost.mipsys.com> (raw)
In-Reply-To: <F14842317963D111817100805F0DFE4D4FFF9A@server1.controlnet.com>
On Thu, Feb 24, 2000, Mark Knecht <mknecht@controlnet.com> wrote:
>According to the LV23 spec the IO_ENB bit is read only, so one would presume
>that writing the a 1 to the IO_ENB ( I presume that this is what is actually
>happening with PCI_COMMAND_IO) would not cause any problems.
>
>As for some of the performance issues, is the Memory Write and Invalidate
>bit in the same PCI register turned off or is it getting turned on? The
>default state is OFF. If not, then DMA writes from the OHCI controller could
>potentially be causing cache flushes and slowing the system down. I am
>presuming here that all or some of the memory addressed by OHCI is marked as
>cacheable which may or may not be the case...)
Hum... I didn't check the driver, but correct handling of cache coherency
issues is not very familiar to most Linux drivers. So I would suggest
sticking with invalidate. Note that I think the bridge will handle
coherency in all cases anyway.
>This may not be visible to something like 'top' because the cache flush it
>is a hardware process in the processor and it is possible that the front
>side bus gets bogged down with cache flush traffic.
Hum, the RAM/cache bus is way much faster than the PCI and in the case of
writes with invalidate, the destination datas is just killed from the CPU
cache, not actually flushed, so this should not cause a significant
performance impact.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-24 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-24 16:58 [Linux1394-devel] Re: FireWire + Apple PB G3: some success Mark Knecht
2000-02-24 19:21 ` Benjamin Herrenschmidt [this message]
2000-03-04 10:30 ` Michel Lanners
-- strict thread matches above, loose matches on Subject: below --
2000-02-24 21:37 Mark Knecht
2000-02-23 10:24 Albrecht Dre_
2000-02-23 23:58 ` Andreas Bombe
2000-02-24 2:44 ` [Linux1394-devel] " Maxim S. Shatskih
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=20000224202131.012502@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mknecht@controlnet.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).