From: Hugh Dickins <hugh@veritas.com>
To: Andrew Morton <akpm@osdl.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: poison struct page for ptlock
Date: Mon, 7 Nov 2005 00:15:05 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.61.0511070006570.30418@goblin.wat.veritas.com> (raw)
In-Reply-To: <20051106160008.28822bbd.akpm@osdl.org>
On Sun, 6 Nov 2005, Andrew Morton wrote:
> Hugh Dickins <hugh@veritas.com> wrote:
> >
> > Suppress split ptlock on arches which may use one page for multiple page
> > tables. Reconsider what better to do (particularly on ppc64) later on.
>
> But why is that a problem per-se? A few "pagetable pages" will share the
> same lock. Deadlocky when we take two pagetable locks?
Good point, it may not be as disastrous as I was imagining. Certainly
deadlocky in copy_page_range and mremap move at present, but that can
be easily surmounted. However, there is the slab lru issue too: if it's
convenient for an arch to use slab cache, I'd prefer not to make life
difficult for them. I'll come back to this but not tonight.
Hugh
prev parent reply other threads:[~2005-11-07 0:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 19:26 Hugh Dickins
2005-11-05 5:32 ` Andrew Morton
2005-11-05 6:40 ` Hugh Dickins
2005-11-05 7:17 ` Andrew Morton
2005-11-06 19:28 ` Andrew Morton
2005-11-06 17:59 ` Anton Blanchard
2005-11-06 19:34 ` Olof Johansson
2005-11-06 22:39 ` Paul Mackerras
2005-11-06 22:57 ` Andrew Morton
2005-11-06 22:58 ` Hugh Dickins
2005-11-06 23:13 ` Andrew Morton
2005-11-06 23:36 ` David S. Miller
2005-11-06 23:48 ` Hugh Dickins
2005-11-07 0:00 ` Andrew Morton
2005-11-07 0:15 ` Hugh Dickins [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=Pine.LNX.4.61.0511070006570.30418@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®