From: Ralf Baechle <ralf@linux-mips.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-arch@vger.kernel.org, Jes Sorensen <jes@trained-monkey.org>
Subject: Re: ia64-specific-dev-mem-handlers.patch
Date: Fri, 11 Mar 2005 00:03:51 +0000 [thread overview]
Message-ID: <20050311000351.GA4820@linux-mips.org> (raw)
In-Reply-To: <20050310121618.1242b2d6.akpm@osdl.org>
On Thu, Mar 10, 2005 at 12:16:18PM -0800, Andrew Morton wrote:
> It is believed that this will be useful to other architectures which allow
> users to uncacheably map RAM. Could interested parties please comment?
MIPS has a very similar problem to solve except that we would ideally
want not 1 but 3 bits in struct page that indicate the cache mode to be
used. This would simplify the use of memory as framebuffer on UMA systems
where neither the normal cache mode of the kernel nor uncached is optimal.
Ralf
next prev parent reply other threads:[~2005-03-11 0:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 20:16 ia64-specific-dev-mem-handlers.patch Andrew Morton
2005-03-11 0:03 ` Ralf Baechle [this message]
2005-03-11 11:16 ` ia64-specific-dev-mem-handlers.patch Jes Sorensen
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=20050311000351.GA4820@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=akpm@osdl.org \
--cc=jes@trained-monkey.org \
--cc=linux-arch@vger.kernel.org \
/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