All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Joel Soete <soete.joel@scarlet.be>
Cc: parisc-linux <parisc-linux@parisc-linux.org>
Subject: Re: [parisc-linux] [patch 2/2] backport of sba sg list management to ccio-dma
Date: Tue, 27 Nov 2007 14:47:43 -0700	[thread overview]
Message-ID: <20071127214743.GA12804@colo.lackof.org> (raw)
In-Reply-To: <JS60WW$8607DD1A85ED3939F455D3059DCDCF43@scarlet.be>

On Tue, Nov 27, 2007 at 01:48:32PM +0100, Joel Soete wrote:
> grr even thought I read well:
> "[snip]
> Hardware Implications
> Cache memory is defined as a small, high-speed block of memory located close
> to the processor. On the HP PA 7200 and PA8000 processors, a portion of the
> software virtual address (called the virtual index) is used as the cache lookup.
> [snip]"
> 
> That's what confusing me, sorry.

You need to read about "VIVT" caches (Virtual Indexed, Virtual Tagged).
The "Virtual Index" bits have to be provided by any cache coherent traffic
in order to be cache coherent. That's how the caches know _where_ in the
cache to find potential hits for a given cacheline.

...
> >  AFAIK U2/U-Turn both are fixed
> > on which page size the support. That would work fine with linux since we
> > just increase the base page size (e.g. 16k or 64k pages for IA64).
> >
> Well, reading further, even thought it seems to be 'programmable':
> "[snip]
> A second feature of this scheme is that it helps limit the overhead of the I/O
> page directory. Recall that the I/O page directory contains all active address
> translations and must be memory-resident. I/O page directory size is equal to
> the size of one entry times 2^k, where k is the number of chain ID bits plus
> the number of block ID bits. The division between the chain ID and the block
> ID is programmable, as is the total number of bits (k), so software can reduce
> the memory overhead of the I/O page directory for systems with smaller I/O
> subsystems if we guarantee that the leading address bits are zero for these
> smaller systems.
> [snip]"
> 
> That said I discover a difference between my d380 and c110 config:
> for c110 no CONFIG_EISA support,
> for d380 CONFIG_EISA yes

EISA introduces a different IOMMU that we haven't written any code for.
We need the "WAX ERS" IIRC.
parisc-linux currently does not support DMA by EISA devices.

...
> So make a difference in HINT_STOP_MOST value.
> Anyway, may be could it help to delay also a bit issue on c110 as on d380 (may
> be enough to re-install the system?)

You can try it and see if it helps.
I don't have U2/U-Turn ERS anymore and thus can not review
the original source of information.

> That siad, the above mentioned paper spoke about "Atomic or locked mode": is
> it this HINT_STOP_MOST which enable this mode?

Sorry - I don't know. My guess is the ERS probably has that info.


...
> What's your idea (afaik a500 didn't use ccio nor ncr53c720)?

You mean "Why test on a500 given A500 doesn't use ccio"?
Just to make sure it's not a generic problem.

In general, I was expecting James Bottomley to have seen issues
with ccio when testing on his C360 (in the past, not recently).

hth,
grant
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2007-11-27 21:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-27 12:48 [parisc-linux] [patch 2/2] backport of sba sg list management to ccio-dma Joel Soete
2007-11-27 21:47 ` Grant Grundler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-11-28  8:25 Joel Soete
2007-11-29 18:50 ` Grant Grundler
2007-11-26  8:48 Joel Soete
2007-11-26 23:27 ` Grant Grundler
     [not found] <JQIT2V$FB9C8381616CCA32E9FC6CC809E8D81D@scarlet.be>
     [not found] ` <20071028064158.GB29233@colo.lackof.org>
     [not found]   ` <4724A084.5090709@scarlet.be>
2007-10-28 15:44     ` Joel Soete
2007-10-29  5:30     ` Grant Grundler
     [not found]     ` <20071029053015.GA14763@colo.lackof.org>
2007-11-01 17:17       ` Joel Soete
     [not found]       ` <472A0A3F.5040007@scarlet.be>
2007-11-02 18:00         ` Joel Soete
2007-11-24 20:36       ` Joel Soete
2007-11-26  3:26         ` Grant Grundler
2007-10-23 16:15 Joel Soete
     [not found] <4714E800.50709@scarlet.be>
2007-10-17 18:44 ` Kyle McMartin
     [not found] ` <20071017184416.GB11502@fattire.cabal.ca>
2007-10-20 17:21   ` Joel Soete
     [not found]   ` <471A3928.8040603@scarlet.be>
2007-10-20 17:23     ` Kyle McMartin
     [not found]     ` <20071020172328.GI10429@fattire.cabal.ca>
2007-10-22  4:39       ` Grant Grundler
     [not found]       ` <20071022043909.GC11869@colo.lackof.org>
2007-11-01 17:18         ` Joel Soete
     [not found]         ` <472A0A49.8010201@scarlet.be>
2007-11-01 21:21           ` Grant Grundler
2007-10-16 16:34 Joel Soete

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=20071127214743.GA12804@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=parisc-linux@parisc-linux.org \
    --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.