From: Krzysztof Halasa <khc@pm.waw.pl>
To: Risto Suominen <risto.suominen@gmail.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH 002/002] de2104x: support for systems lacking cache coherence
Date: Mon, 09 Feb 2009 17:58:25 +0100 [thread overview]
Message-ID: <m3vdrja6oe.fsf@intrepid.localdomain> (raw)
In-Reply-To: <46e1c7760902090022g1d903ca0nf314f0c1cc6b07c8@mail.gmail.com> (Risto Suominen's message of "Mon\, 9 Feb 2009 10\:22\:15 +0200")
Risto Suominen <risto.suominen@gmail.com> writes:
>> 1) {pci,dma}_alloc_{consistent,coherent}() give kernel mappings of
>> the buffer with the cache disabled.
^^^^^^^^^^^^^^^^^^^^^^^
> Sounds good, but does not seem to help. My theory is that when the cpu
> is writing to one descriptor, it accidentally overwrites another
> descriptor, that has already been written to by the device, as there
> is only a single dirty bit, that makes the whole cacheline to be
> flushed.
That means the consistent/coherent mapping isn't really
consistent/coherent (uncached), right? Perhaps there is some way to fix
this instead of changing the drivers to avoid the problematic area?
Potentially any driver is affected by such coherency problem, this can't
be specific to 21040.
--
Krzysztof Halasa
next prev parent reply other threads:[~2009-02-09 16:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46e1c7760902071330i5362fe4fvd99fc7075fc666d3@mail.gmail.com>
2009-02-09 7:27 ` Fwd: [PATCH 002/002] de2104x: support for systems lacking cache coherence Risto Suominen
2009-02-09 7:45 ` David Miller
2009-02-09 8:22 ` Risto Suominen
2009-02-09 8:29 ` David Miller
2009-02-09 8:35 ` Risto Suominen
2009-02-09 16:58 ` Krzysztof Halasa [this message]
2009-02-09 19:22 ` Risto Suominen
2009-02-09 22:51 ` David Miller
2009-02-10 1:45 ` Krzysztof Halasa
2009-02-10 1:50 ` David Miller
2009-02-10 23:21 ` David Miller
2009-02-11 12:18 ` Risto Suominen
2009-02-11 12:31 ` Risto Suominen
2009-02-11 21:39 ` David Miller
2009-02-13 3:42 ` Benjamin Herrenschmidt
2009-02-10 1:01 ` Andrew Morton
2009-02-10 1:07 ` David Miller
2009-02-10 7:16 ` Risto Suominen
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=m3vdrja6oe.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=risto.suominen@gmail.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