From: Quinn Jensen <jensenq@Lineo.COM>
To: jsun@hermes.mvista.com
Cc: Ralf Baechle <ralf@oss.sgi.com>, linux-mips@oss.sgi.com
Subject: Re: NFS root with cache on
Date: Mon, 05 Feb 2001 14:14:47 -0700 [thread overview]
Message-ID: <3A7F17C7.4070406@Lineo.COM> (raw)
In-Reply-To: 3A7EFBC7.9B7D6AF9@mvista.com
jsun@hermes.mvista.com wrote:
>>
>> I have tried that in this case but it didn't help,
>> because the receive skb data pointers all point to
>> the KSEG0 view of the data anyway.
>
>
> I looked into similar problems a while back. If I remeber correctly, the data
> pointers do point to kseg0. It is up to the driver to do appropriate
> dma_cache_invalidate() (or some functions to that effect) at certain places.
Yes, the tulip driver calls pci_unmap_single() on the receive
buffer, but for mips (in asm-mips/pci.h) this call does
nothing. And this is what is so confusing. Only if the
receive buffer was forced to be in KSEG1 would this make
sense.
>
> What is the CPU? It seems logical to suspect about the dma cache routines.
Yes, I have scrubbed over my patch to the cache routines
many times, especially since on the IDT 334 the cache-way
selection for indexed cache ops is weird--they left the
way-bit up at bit 12 as if it were an 8KB cache, when
in reality it is only a 2KB cache.
Quinn
next prev parent reply other threads:[~2001-02-05 21:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 20:34 NFS root with cache on Quinn Jensen
2001-02-05 3:44 ` Ralf Baechle
2001-02-05 16:50 ` Quinn Jensen
2001-02-05 16:55 ` Kevin D. Kissell
2001-02-05 16:55 ` Kevin D. Kissell
2001-02-05 18:07 ` Jun Sun
2001-02-05 18:42 ` Quinn Jensen
2001-02-05 19:15 ` Jun Sun
2001-02-05 21:14 ` Quinn Jensen [this message]
2001-02-05 19:50 ` Ralf Baechle
2001-02-05 21:13 ` netbooting indy - update, elf2ecoff? Kenneth C Barr
2001-02-05 21:13 ` Kenneth C Barr
2001-02-06 6:32 ` Geert Uytterhoeven
2001-02-06 18:07 ` Klaus Naumann
2001-02-06 20:24 ` Florian Lohoff
2001-02-05 21:39 ` NFS root with cache on Alan Cox
2001-02-05 21:39 ` Alan Cox
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=3A7F17C7.4070406@Lineo.COM \
--to=jensenq@lineo.com \
--cc=jsun@hermes.mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.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