From: Richard Yao <ryao@gentoo.org>
To: Kernel development list <linux-kernel@vger.kernel.org>
Subject: Is there anyway to do direct mapped cache on Intel hardware?
Date: Mon, 18 May 2015 14:07:30 -0400 [thread overview]
Message-ID: <555A2A62.80309@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
Is there anyway to do direct mapped cache on Intel hardware?
Direct mapped cache should allow me to implement software ECC via the
low memory / high memory split. It would be slow, but I would prefer to
have a slow laptop than one that is vulnerable to bit flips.
If direct mapped cache is possible and non-NUMA systems could avoid
writing it back/through, I imagine that people could also protect
against cold boot attacks by encrypting main memory. This would be also
be slow, but the AES instructions that Intel's newer processors are
supposed to have should keep the slowdown within some reasonable bound.
There might also be applications for using external memory algorithms
(e.g. fractal tree indexes) to speed up in-memory operations. I also am
not sure if the difference between system memory and cache is big enough
to make it a win, but I am sure that is not something that I would want
to implement on my laptop in my spare time.
If someone knows a way to do direct mapped cache, please share.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2015-05-18 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 18:07 Richard Yao [this message]
2015-05-18 18:33 ` Is there anyway to do direct mapped cache on Intel hardware? Richard Yao
2015-07-01 9:35 ` Pavel Machek
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=555A2A62.80309@gentoo.org \
--to=ryao@gentoo.org \
--cc=linux-kernel@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