From: Andi Kleen <andi@firstfloor.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Felix Rubinstein <felixru@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: /dev/mem implementation
Date: Mon, 18 Jan 2010 11:22:04 +0100 [thread overview]
Message-ID: <87hbqj4ss3.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20100117094043.0483ee1a@infradead.org> (Arjan van de Ven's message of "Sun, 17 Jan 2010 09:40:43 -0800")
Arjan van de Ven <arjan@infradead.org> writes:
>
> If you feel that you have a valid use case where you really want do
> muck with such memory, it might be a good idea to explain that
> usecase....
To add to it this only applies to uncacheable pages which don't use
MTRRs. Unless in some special situations (e.g. a lot of GPU 3d data
active) that situation tends to be rare and not apply to most memory.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-01-18 10:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 16:47 /dev/mem implementation Felix Rubinstein
2010-01-17 17:40 ` Arjan van de Ven
2010-01-18 10:22 ` Andi Kleen [this message]
2010-01-18 12:18 ` Felix Rubinstein
2010-01-18 15:16 ` Arjan van de Ven
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=87hbqj4ss3.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=arjan@infradead.org \
--cc=felixru@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.