From: rubisher <rubisher@scarlet.be>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: dave <dave@hiauly1.hia.nrc.ca>,
"James.Bottomley" <James.Bottomley@HansenPartnership.com>,
"soete.joel" <soete.joel@scarlet.be>,
linux-parisc <linux-parisc@vger.kernel.org>,
kyle <kyle@parisc-linux.org>, matthew <matthew@wil.cx>
Subject: Re: Yet another ccio fix idea?
Date: Sat, 15 Mar 2008 19:32:55 +0000 [thread overview]
Message-ID: <47DC2467.3070502@scarlet.be> (raw)
In-Reply-To: <20080314060251.GJ24794@colo.lackof.org>
Grant Grundler wrote:
[snip]
>> PS: in this doc feb96a6.pdf (easy to find) it was said:
>> "[snip]
>> Entries in the PA 7200 and PA 8000 caches are stored in lines
>> of 32 bytes.
>> [snip]
>>
>> Because one-word writes occur in the I/O system, for registers,
>> semaphores, or short DMA writes it was necessary that the I/O
>> adapter implement a one-line-deep cache to buffer cache lines,
>> so that these one-word writes could be executed by performing
>> a coherent read private transaction on the Runway bus, obtaining
>> the most recent copy of the cache line, modifying it locally in
>> cache, and finally writing the modified line back to main memory.
> ...
>
>> 2 thinks:
>> - it seems to confirm that cache line is well 32bytes wide ;-)
>>
>> - for 'one word writes...' how should it be implemented?
>
> "one word writes" refers to DMA writes, not CPU writes.
>
(tx it's not always easy to follow the master and the slave in this story)
>> It look like the sba_iommu driver:
>> "READ_REG(ioc-ioc_ha_IOC_PCOM); /* flush purges */
>> but without more detailed docs on U2/UTurn ccio, I don't know how to
>> implement matter, sorry.
>
> The IOMMU driver programs the IO Pdir with the results of "lci" instruction
> and this should be all the IOMMU needs to coherently read/modify/write
> the cacheline that the "one word" DMA write is targeting. In short,
> it's already implemented or I'd think we'd see much worse problems
> on ccio platforms.
>
> hth,
> grant
>
Ok.
Just one thought because in the backport I did on ccio of your job on sba (which seems to works for me as well as previous
stuff, may be a bit better for system low in ram like my c110), it was one of the matter related to io coherency which I
didn't reach to backport?
Tx again,
r.
next prev parent reply other threads:[~2008-03-15 19:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 9:16 Yet another ccio fix idea? rubisher
2008-03-12 11:47 ` James Bottomley
2008-03-12 12:51 ` John David Anglin
2008-03-12 19:52 ` John David Anglin
2008-03-14 3:57 ` Grant Grundler
2008-03-14 6:02 ` Grant Grundler
2008-03-15 19:21 ` [Patch] ccio-dma.c [Was: Yet another ccio fix idea?] rubisher
2008-03-19 6:19 ` Grant Grundler
2008-03-15 19:32 ` rubisher [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-14 14:18 Yet another ccio fix idea? rubisher
2008-03-14 8:30 rubisher
2008-03-14 15:35 ` John David Anglin
2008-03-15 12:03 ` rubisher
2008-03-10 17:16 rubisher
2008-03-10 17:26 ` John David Anglin
2008-03-14 5:53 ` Grant Grundler
2008-03-09 13:55 Joel Soete
2008-03-09 17:46 ` Grant Grundler
2008-03-09 17:48 ` Grant Grundler
2008-03-10 19:59 ` James Bottomley
2008-03-10 20:37 ` John David Anglin
2008-03-14 3:50 ` Grant Grundler
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=47DC2467.3070502@scarlet.be \
--to=rubisher@scarlet.be \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=grundler@parisc-linux.org \
--cc=kyle@parisc-linux.org \
--cc=linux-parisc@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=soete.joel@scarlet.be \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.