From: David VomLehn <dvomlehn@cisco.com>
To: "Jon Fraser [jfraser"@broadcom.com], linux-mips@linux-mips.org
Subject: Re: [PATCH 2.6.24][MIPS]Work in progress: fix HIGHMEM-enabled dcache flushing on 32-bit processor
Date: Wed, 02 Apr 2008 14:56:47 -0700 [thread overview]
Message-ID: <47F4011F.9020604@cisco.com> (raw)
> Did this fix your NFS problem?
>
> I'm working on discontiguous memory platforms as well.
>
> Jon Fraser
>
> On Wed, 2008-03-12 at 19:31 -0700, David VomLehn wrote:
>> This patch is a work in progress, per Ralf's suggestion from last
>> week. It is intended to fix dcache flushing issues when using HIGHMEM
>> support. We get much better results with this patch applied, but I
>> would not characterize our 2.6.24 port as stable, yet, so there may be other HIGHMEM-related issues.
Yes, we are able to boot using NFS with this patch. There are some other minor
changes that appear necessary for correct cache flushing but which don't seem to
be causing any actual issues. (Cache stuff just works that way--you don't know
you've got a problem until you get into some obscure corner case). I'll post
these as soon as I can get to it.
I can't say whether these are all the changes required for high memory support,
but we sure get a lot farther when we use them...
--
David VomLehn, dvomlehn@cisco.com
The opinions expressed herein are likely mine, but might not be my employer's...
WARNING: multiple messages have this Message-ID (diff)
From: David VomLehn <dvomlehn@cisco.com>
To: "Jon Fraser [jfraser"@broadcom.com, linux-mips@linux-mips.org
Subject: Re: [PATCH 2.6.24][MIPS]Work in progress: fix HIGHMEM-enabled dcache flushing on 32-bit processor
Date: Wed, 02 Apr 2008 14:56:47 -0700 [thread overview]
Message-ID: <47F4011F.9020604@cisco.com> (raw)
Message-ID: <20080402215647.GxlDtN2DvTQ85aZaeHzNggzH64JTn2ujdXyrDWUREgE@z> (raw)
> Did this fix your NFS problem?
>
> I'm working on discontiguous memory platforms as well.
>
> Jon Fraser
>
> On Wed, 2008-03-12 at 19:31 -0700, David VomLehn wrote:
>> This patch is a work in progress, per Ralf's suggestion from last
>> week. It is intended to fix dcache flushing issues when using HIGHMEM
>> support. We get much better results with this patch applied, but I
>> would not characterize our 2.6.24 port as stable, yet, so there may be other HIGHMEM-related issues.
Yes, we are able to boot using NFS with this patch. There are some other minor
changes that appear necessary for correct cache flushing but which don't seem to
be causing any actual issues. (Cache stuff just works that way--you don't know
you've got a problem until you get into some obscure corner case). I'll post
these as soon as I can get to it.
I can't say whether these are all the changes required for high memory support,
but we sure get a lot farther when we use them...
--
David VomLehn, dvomlehn@cisco.com
The opinions expressed herein are likely mine, but might not be my employer's...
next reply other threads:[~2008-04-02 21:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 21:56 David VomLehn [this message]
2008-04-02 21:56 ` [PATCH 2.6.24][MIPS]Work in progress: fix HIGHMEM-enabled dcache flushing on 32-bit processor David VomLehn
-- strict thread matches above, loose matches on Subject: below --
2008-11-04 18:07 Lance Richardson
2008-11-04 20:09 ` David VomLehn
2008-03-13 2:31 David VomLehn
2008-04-02 19:14 ` Jon Fraser
2008-04-18 18:00 ` Jon Fraser
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=47F4011F.9020604@cisco.com \
--to=dvomlehn@cisco.com \
--cc="Jon Fraser [jfraser"@broadcom.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