From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jan Beulich <jbeulich@novell.com>
Cc: Hugh Dickins <hugh@veritas.com>,
Jeremy Fitzhardinge <jeremy@goop.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: Sat, 17 May 2008 10:27:43 -0500 [thread overview]
Message-ID: <1211038063.8297.133.camel@pasglop> (raw)
In-Reply-To: <482DC4A9.76E4.0078.0@novell.com>
On Fri, 2008-05-16 at 16:30 +0100, Jan Beulich wrote:
> >>> 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.
In my patches, I did drop the double indirection and just updated the
fields inside of the batch. Worked fine.
Ben.
next prev parent reply other threads:[~2008-05-17 15:39 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 ` [PATCH] remove double indirection on tlb parameter to free_pgd_range()& Co Jan Beulich
2008-05-16 16:31 ` Hugh Dickins
2008-05-17 15:27 ` Benjamin Herrenschmidt [this message]
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=1211038063.8297.133.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=andrea@qumranet.com \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=jbeulich@novell.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