From: Hugh Dickins <hughd@google.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org,
Jeremy Fitzhardinge <jeremy@goop.org>,
Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: mmotm threatens ppc preemption again
Date: Sun, 20 Mar 2011 19:20:18 -0700 (PDT) [thread overview]
Message-ID: <alpine.LSU.2.00.1103201901340.7257@sister.anvils> (raw)
In-Reply-To: <1300672207.2402.205.camel@pasglop>
On Mon, 21 Mar 2011, Benjamin Herrenschmidt wrote:
>
> As long as the races to avoid are between map/unmap vs. access, yes, it
> -should- be fine, and we used to not do demand faulting on kernel space
> (but for how long ?). I'm wondering why we don't just stick a ptl in
> there or is there a good reason why we can't ?
We can - but we usually prefer to avoid unnecessary locking.
An arch function which locks init_mm.page_table_lock on powerpc,
but does nothing on others?
Hugh
next prev parent reply other threads:[~2011-03-21 2:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 4:11 mmotm threatens ppc preemption again Hugh Dickins
2011-03-20 23:53 ` Benjamin Herrenschmidt
2011-03-21 1:41 ` Hugh Dickins
2011-03-21 1:50 ` Benjamin Herrenschmidt
2011-03-21 2:20 ` Hugh Dickins [this message]
2011-03-21 2:22 ` Benjamin Herrenschmidt
2011-03-30 20:53 ` Andrew Morton
2011-03-30 21:07 ` Jeremy Fitzhardinge
2011-03-31 0:52 ` Benjamin Herrenschmidt
2011-03-31 17:21 ` Jeremy Fitzhardinge
2011-03-31 20:38 ` Benjamin Herrenschmidt
2011-05-18 23:29 ` Jeremy Fitzhardinge
2011-03-21 11:24 ` Jeremy Fitzhardinge
2011-03-21 22:52 ` Benjamin Herrenschmidt
2011-03-22 13:34 ` Jeremy Fitzhardinge
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=alpine.LSU.2.00.1103201901340.7257@sister.anvils \
--to=hughd@google.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=jeremy@goop.org \
--cc=linuxppc-dev@lists.ozlabs.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