From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Alok kataria <alokkataria1@gmail.com>, Andi Kleen <ak@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: ARCH_FREE_PTE_NR 5350 on x86_64
Date: Tue, 23 Oct 2007 06:29:18 +1000 [thread overview]
Message-ID: <1193084958.6745.99.camel@pasglop> (raw)
In-Reply-To: <Pine.LNX.4.64.0710221913250.18548@blonde.wat.veritas.com>
> Agreed. No hurry, but thanks to Alok for reminding us.
> CC'ing Ben since he's the one most active in mmu_gathering these days.
> CC'ing Thomas lest he's puzzling over it in the x86 merge.
Hrm... yes, that stuff sucks. I've had my work on mmu gather on hold
since KS due to other priorities showing up, but I'll get back to it
soon and put that on the todo list.
The main pain here is the immap_lock. I have various plans to get rid of
preemption blocking in the main mmu gather (the stuff we discussed
already basically), but the immap_lock must stay, so we need to keep
something akin to immap_lock.
With the new approach, the disconnect between ZAP_BLOCK_SIZE and
whatever we use to represent the size of a batch might still be relevant
for the cases where we aren't holding that lock.
I'll get back to that stuff soon and we can then discuss the details.
Ben.
prev parent reply other threads:[~2007-10-22 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 6:54 ARCH_FREE_PTE_NR 5350 on x86_64 Alok kataria
2007-10-15 12:36 ` Nick Piggin
2007-10-22 18:22 ` Hugh Dickins
2007-10-22 20:29 ` Benjamin Herrenschmidt [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=1193084958.6745.99.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=ak@suse.de \
--cc=alokkataria1@gmail.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=tglx@linutronix.de \
/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