Re: [RFC] MMIO accessors & barriers documentation


ioremap_wc is actually the easy half. I have an old patch that handles
that. The trick is to make certain multiple people don't map the same
thing with different attributes. Unfortunately I haven't had time to
work through that one yet.

Actually, that's interesting because I need the exactly oposite on
PowerPC I think.... That is people will -need- to do both a wc and a
non-wc mapping if they want to be able to issue stores that are
guaranteed not to be combined.

The problem I've seen is that at least one processor (the Cell) and
maybe more seem to be combining between threads on the same CPU (unless
the stores are issues to a guarded mapping which prevents combining
completely, that is the sort of mapping we currently do with ioremap).

That means that it's impossible to prevent combining with explicit
barriers. For example:

Thread 0 Thread 1
store to A store to A+1
barrier barrier
\ /
\ /
\ /
Store unit might sees:
store to A
store to A+1
barrier
barrier

That is the stores aren't tagged with their source thread and thus the
non cacheable store unit will not prevent combining between them.

Again, it might just be a Cell CPU bug in which case we may have to just
disable use of WC on that processor, period. But it might be a more
generic problem too, we need to investigate.

If the problem ends up being widespread, the only ways I see to prevent
the combining from happening are to do a dual mapping as I explained
earlier, or maybe to have drivers always do the stores that must not be
combine as part of spinlocks, with appropriate use of
io_to_lock_barrier() (mmiowb()).

Anyway, let's not pollute this discussion with that too much now :)

Ben.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Multi Locations trick
    ... We have about 50 stores and each of them uploads its daily data to a nfs ... 2-The directory names are also storeIDs and I need to use this StoreID in ... the output of the mapping. ...
    (microsoft.public.biztalk.general)
  • [PATCH] doc: fix typos in Documentation/memory-barriers.txt
    ... A write barrier is a partial ordering on stores only; ... A CPU can be viewed as as commiting a sequence of store operations to the ... it may also mapped as a virtual I/O space in the CPU's ...
    (Linux-Kernel)
  • Re: [PATCH 2/4] Add replace_page(), change the mapping of pte from one page into another
    ... other side already got the oldpage) ... But there's no barrier there, ... store part of that sequence is prevented from passing stores, ... depends on the result of the LL/SC, so that has to be complete. ...
    (Linux-Kernel)
  • Re: [PATCH RESEND] Minimal fix for private_list handling races
    ... its stores to clear b_assoc_buffers propagate to the CPU running ... So if there is a!dirty buffer on the list, ... that was actually the reason why I changed the checks from ... so I'll add the barrier and ...
    (Linux-Kernel)
  • Re: Memory fence instructions on x86
    ... semantics and ordinary stores have release semantics. ... depend on whether the loads and stores are to the same location. ... release barrier. ... the load and store being to different locations. ...
    (comp.programming.threads)