From: Zachary Amsden <zach@vmware.com>
To: David Rientjes <rientjes@google.com>
Cc: Hugh Dickins <hugh@veritas.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [patch -mm] i386: use pte_update_defer in ptep_test_and_clear_{dirty,young}
Date: Mon, 16 Apr 2007 15:08:47 -0700 [thread overview]
Message-ID: <4623F3EF.9040406@vmware.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0704161217310.12685@chino.kir.corp.google.com>
David Rientjes wrote:
> Sure, but what I really like about the patch is that we're only flushing
> something if !flush_end in the first place. So we can eliminate any TLB
> flushing if that VMA didn't need it; that's a change from the current
> behavior. And since the most obvious use-case for /proc/pid/clear_refs is
> in conjunction with /proc/pid/smaps for approximating memory footprint,
> we'll end up saving TLB flushes because the granularity with which that
> measurement is taken is usually very fine.
>
> Acked-by: David Rientjes <rientjes@google.com>
>
I like the patch even better if you still batch the flushes, but keep
the !flush_end machinery. If I read it correctly, flush_start stays at
the lower bound for the whole function, so it is still accurate later.
And with the flush outside the spinlock, contention time is lower.
Thanks,
Zach
next prev parent reply other threads:[~2007-04-16 22:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 6:37 [patch -mm] i386: use pte_update_defer in ptep_test_and_clear_{dirty,young} David Rientjes
2007-03-26 9:08 ` Andrew Morton
2007-03-26 20:24 ` Zachary Amsden
2007-04-13 17:54 ` Hugh Dickins
2007-04-13 19:05 ` Zachary Amsden
2007-04-13 19:27 ` Zachary Amsden
2007-04-13 20:24 ` Hugh Dickins
2007-04-13 20:59 ` Zachary Amsden
2007-04-16 17:59 ` Hugh Dickins
2007-04-16 18:51 ` David Rientjes
2007-04-16 19:04 ` Hugh Dickins
2007-04-16 19:20 ` David Rientjes
2007-04-16 22:08 ` Zachary Amsden [this message]
2007-04-16 22:00 ` Zachary Amsden
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=4623F3EF.9040406@vmware.com \
--to=zach@vmware.com \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
/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