All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Russell King <rmk@arm.linux.org.uk>, linux-mm@kvack.org
Subject: Re: PTE aging, ptep_test_and_clear_young() and TLB
Date: Sun, 18 Apr 2004 08:52:19 -0700	[thread overview]
Message-ID: <20040418155219.GA743@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0404181142290.12120-100000@localhost.localdomain>

On Sun, Apr 18, 2004 at 11:58:21AM +0100, Hugh Dickins wrote:
> mm and address are directly available in both mine and Andrea's (the
> difference between us is finding vma: mine needs find_vma in the anon
> case, on Andrea's it's directly available), shouldn't be any need to
> add in that ppc/ppc64 code.
> Hmm, maybe I didn't look hard enough at it, and could have just taken
> it out of ppc/ppc64, instead of moving it from generic; I'll go back
> and check on that sometime.
> I'm not surprised Russell's found he just needs mm rather than vma,
> I did try briefly yesterday to understand just what it is that vma
> gives to flush TLB.  Needs thorough research through all the arches,
> the ARM case is not necessarily representative.
> Wouldn't surprise me if it turns out vma necessary on some in the
> file-backed case, but on none in the anon case (would then cease
> to be a differentiator between anonmm and anon_vma if so).

I have to confess to not looking closely at the recent merge-oriented
code. Passing the things in when they're available will do it.


On Sun, Apr 18, 2004 at 11:58:21AM +0100, Hugh Dickins wrote:
> But I still think that we'd want to cut down on the intercpu TLB
> flushes for page_referenced, should batch them up to some extent.
> Russell may well be right that we're much too lazy about the
> referenced bit in 2.6, but that doesn't mean we now have to
> jump and get it exactly right all the time: the dirty bit is
> vital, the referenced bit never more than a hint.

I'm not foreseeing many effective algorithms for batching TLB flushes
there. Maybe something will get brewed up that surprises me.


-- wli
--
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:"aart@kvack.org"> aart@kvack.org </a>

  parent reply	other threads:[~2004-04-18 15:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-17 20:15 PTE aging, ptep_test_and_clear_young() and TLB Russell King
2004-04-17 20:43 ` William Lee Irwin III
2004-04-18  9:36   ` Russell King
2004-04-18  9:39     ` William Lee Irwin III
2004-04-18 10:58       ` Hugh Dickins
2004-04-18 11:23         ` Russell King
2004-04-18 12:36           ` Hugh Dickins
2004-04-18 12:42             ` Russell King
2004-04-18 19:55               ` Russell King
2004-04-18 20:01                 ` Russell King
2004-04-18 23:14                 ` Hugh Dickins
2004-04-18 23:34                   ` Russell King
2004-04-18 15:52         ` William Lee Irwin III [this message]
2004-04-18 10:42     ` Russell King
2004-04-18 15:12       ` William Lee Irwin III
2004-04-17 22:27 ` Hugh Dickins
2004-04-17 23:47   ` Anton Blanchard

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=20040418155219.GA743@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=hugh@veritas.com \
    --cc=linux-mm@kvack.org \
    --cc=rmk@arm.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.