From: Andrew Morton <akpm@osdl.org>
To: "Martin J. Bligh" <mbligh@mbligh.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] mm: remove global locks from mm/highmem.c
Date: Mon, 29 Jan 2007 17:41:18 -0800 [thread overview]
Message-ID: <20070129174118.0e922ab3.akpm@osdl.org> (raw)
In-Reply-To: <45BE9FE8.4080603@mbligh.org>
On Mon, 29 Jan 2007 17:31:20 -0800
"Martin J. Bligh" <mbligh@mbligh.org> wrote:
> Peter Zijlstra wrote:
> > On Sun, 2007-01-28 at 14:29 -0800, Andrew Morton wrote:
> >
> >> As Christoph says, it's very much preferred that code be migrated over to
> >> kmap_atomic(). Partly because kmap() is deadlockable in situations where a
> >> large number of threads are trying to take two kmaps at the same time and
> >> we run out. This happened in the past, but incidences have gone away,
> >> probably because of kmap->kmap_atomic conversions.
> >
> >> From which callsite have you measured problems?
> >
> > CONFIG_HIGHPTE code in -rt was horrid. I'll do some measurements on
> > mainline.
> >
>
> CONFIG_HIGHPTE is always horrid -we've known that for years.
We have? What's wrong with it? <looks around for bug reports>
> Don't use it.
>
> If that's all we're fixing here, I'd be highly suspect ...
highpte uses atomic kmaps - it is unrelated to this work.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-01-30 1:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-28 14:11 Peter Zijlstra
2007-01-28 14:49 ` Christoph Hellwig
2007-01-28 15:17 ` Ingo Molnar
2007-01-28 15:28 ` Christoph Hellwig
2007-01-28 15:48 ` Ingo Molnar
2007-01-28 15:54 ` Christoph Hellwig
2007-01-28 18:19 ` Ingo Molnar
2007-01-28 22:29 ` Andrew Morton
2007-01-29 2:52 ` Nick Piggin
2007-01-29 9:44 ` Peter Zijlstra
2007-01-30 1:31 ` Martin J. Bligh
2007-01-30 1:41 ` Andrew Morton [this message]
2007-01-30 1:49 ` Martin J. Bligh
2007-01-30 2:15 ` Andrew Morton
2007-01-31 0:44 ` David Chinner
2007-01-31 1:11 ` Andrew Morton
2007-01-31 3:22 ` David Chinner
2007-02-02 12:05 ` Christoph Hellwig
2007-02-02 19:24 ` Matt Mackall
2007-02-02 23:16 ` David Chinner
2007-02-02 23:14 ` David Chinner
2007-01-29 19:08 ` Ingo Molnar
2007-01-29 19:19 ` Hugh Dickins
2007-01-29 19:53 ` Ingo Molnar
2007-01-29 20:06 ` Ingo Molnar
2007-01-30 2:02 ` Nick Piggin
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=20070129174118.0e922ab3.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@mbligh.org \
--cc=mingo@elte.hu \
/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