From: "Jan Beulich" <jbeulich@novell.com>
To: "Hugh Dickins" <hugh@veritas.com>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"Andrea Arcangeli" <andrea@qumranet.com>,
"Christoph Lameter" <clameter@sgi.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] remove double indirection on tlb parameter to free_pgd_range()& Co
Date: Fri, 16 May 2008 16:30:17 +0100 [thread overview]
Message-ID: <482DC4A9.76E4.0078.0@novell.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0805161517510.8758@blonde.site>
>>> Hugh Dickins <hugh@veritas.com> 16.05.08 16:39 >>>
> Pass mmu_gather** in the
> public interfaces, since we might want to add latency lockdrops later;
> but no attempt to do so yet, going by vma should itself reduce latency.
>...
>But, returning to the start, please let's hold yours back after all.
If you want to keep and actively use the double indirection, would you
guarantee current semantics like ->mm and ->fullmm to always be what
was specified at the start of the operation? Verifying this was what
made me go through that call tree in the first place, and obviously this
is harder to verify when there is potential for the whole structure
pointed to to be replaced by another one.
Jan
next prev parent reply other threads:[~2008-05-16 15:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 14:47 [PATCH] remove double indirection on tlb parameter to free_pgd_range() & Co Jan Beulich
2008-05-16 8:12 ` Jeremy Fitzhardinge
2008-05-16 14:39 ` Hugh Dickins
2008-05-16 15:30 ` Jan Beulich [this message]
2008-05-16 16:31 ` [PATCH] remove double indirection on tlb parameter to free_pgd_range()& Co Hugh Dickins
2008-05-17 15:27 ` Benjamin Herrenschmidt
2008-05-17 15:27 ` [PATCH] remove double indirection on tlb parameter to free_pgd_range() & Co Benjamin Herrenschmidt
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=482DC4A9.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=andrea@qumranet.com \
--cc=benh@kernel.crashing.org \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.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