linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: 'Hugh Dickins' <hugh@veritas.com>, Christoph Lameter <clameter@sgi.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
	David Howells <dhowells@redhat.com>,
	Rohit Seth <rohitseth@google.com>,
	linux-mm@kvack.org
Subject: RE: tracking dirty pages patches
Date: Tue, 23 May 2006 14:17:05 -0700	[thread overview]
Message-ID: <000001c67eae$3e29bd90$e734030a@amr.corp.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0605232131560.19019@blonde.wat.veritas.com>

Hugh Dickins wrote on Tuesday, May 23, 2006 1:34 PM
> On Tue, 23 May 2006, Christoph Lameter wrote:
> > 
> > That is true for ia64. However, the name "lazy_mmu_prot_update" suggests
> > that the intended scope is to cover protection updates in general. 
> > And we definitely change the protections of the page.
> 
> True, and I now see Documentation/cachetlb.txt documents it that way.
> Yet nothing but ia64 has any use for it.
> 
> > Maybe we could rename lazy_mmu_prot_update? What does icache/dcache 
> > aliasing have to do with page protection?
> 
> I'd strongly agree with you that it should be renamed: for a start,
> why does it say "lazy"?  That's an architectural implementation detail.
> 
> Except that, instead of agreeing it should be renamed, I say it should
> be deleted entirely.  It seems to represent that ia64 has an empty
> update_mmu_cache, and someone decided to add a new interface instead
> of giving ia64 that work to do in its update_mmu_cache.

My memory recollects that it was done just like what you suggested:
overloading update_mmu_cache for ia64, but it was vetoed by several mm
experts.  And as a result a new function was introduced.

- Ken

--
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>

  parent reply	other threads:[~2006-05-23 21:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-22 19:31 Hugh Dickins
2006-05-22 20:29 ` Andrew Morton
2006-05-23  8:17   ` Nick Piggin
2006-05-23 14:55   ` Hugh Dickins
2006-05-23 16:24 ` Christoph Lameter
2006-05-23 19:21   ` Hugh Dickins
2006-05-23 19:31     ` Christoph Lameter
2006-05-23 20:34       ` Hugh Dickins
2006-05-23 21:16         ` Christoph Lameter
2006-05-23 21:17         ` Chen, Kenneth W [this message]
2006-05-23 21:40           ` update_mmu_cache vs. lazy_mmu_prot_update Christoph Lameter
2006-05-24 14:12             ` Hugh Dickins
2006-05-23 22:28         ` remove VM_LOCKED before remap_pfn_range and drop VM_SHM Christoph Lameter
2006-05-24 14:57           ` Hugh Dickins
2006-05-24  2:25         ` tracking dirty pages patches Arjan van de Ven
2006-05-24 15:10           ` Hugh Dickins
2006-05-25  2:26             ` Arjan van de Ven
2006-05-23 16:41 ` David Howells
2006-05-23 23:07 ` Peter Zijlstra
2006-05-24 14:20   ` Hugh Dickins

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='000001c67eae$3e29bd90$e734030a@amr.corp.intel.com' \
    --to=kenneth.w.chen@intel.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=dhowells@redhat.com \
    --cc=hugh@veritas.com \
    --cc=linux-mm@kvack.org \
    --cc=rohitseth@google.com \
    --cc=torvalds@osdl.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