From: Andrea Arcangeli <andrea@suse.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, olof@austin.ibm.com
Subject: Re: [PATCH] .text page fault SMP scalability optimization
Date: Sun, 30 Oct 2005 15:44:59 +0100 [thread overview]
Message-ID: <20051030144459.GB5074@opteron.random> (raw)
In-Reply-To: <1130653052.29054.237.camel@gaston>
On Sun, Oct 30, 2005 at 05:17:31PM +1100, Benjamin Herrenschmidt wrote:
> Note that we should really pass more than just "write_access" from the
> arch code. We could make good use of "execute" in some cases as well,
Indeed. Bitflags sounds the most efficient way to do that. Currently
write_access is 0/1 value only.
> also knowing wether this is a real fault or the result of
> get_user_pages() (in some case, the former could use more agressive TLB
> pre-loading, not the later). Finally, those infos should be passed to
> update_mmu_cache().
Interesting.
prev parent reply other threads:[~2005-10-30 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 7:52 [PATCH] .text page fault SMP scalability optimization Andrea Arcangeli
2005-10-19 8:14 ` Andrew Morton
2005-10-19 9:06 ` Andrea Arcangeli
2005-10-30 6:17 ` Benjamin Herrenschmidt
2005-10-30 14:44 ` Andrea Arcangeli [this message]
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=20051030144459.GB5074@opteron.random \
--to=andrea@suse.de \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@austin.ibm.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 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.