All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Paul Cameron Davies <pauld@cse.unsw.EDU.AU>
Cc: Andrew Morton <akpm@osdl.org>,
	David Singleton <dsingleton@mvista.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Lee.Schermerhorn@hp.com
Subject: Re: new procfs memory analysis feature
Date: Fri, 08 Dec 2006 13:46:10 -0800	[thread overview]
Message-ID: <4579DD22.70609@goop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0612081716440.28861@weill.orchestra.cse.unsw.EDU.AU>

Paul Cameron Davies wrote:
> The PTI gathers all the open coded iterators togethers into one place,
> which would be a good precursor to providing generic iterators for
> non performance critical iterations.
>
> We are completing the updating/enhancements to this PTI for the latest
> kernel, to be released just prior to LCA.  This PTI is benchmarking
> well. We also plan to release the experimental guarded page table
> (GPT) running under this PTI.

I looked at implementing linear pagetable mappings for x86 as a way of
getting rid of CONFIG_HIGHPTE, and to make pagetable manipulations
generally more efficient.  I gave up on it after a while because all the
existing pagetable accessors are not suitable for a linear pagetable,
and I didn't want to have to introduce a pile of new pagetable
interfaces.  Would the PTI interface be helpful for this?

Thanks,
    J

WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Paul Cameron Davies <pauld@cse.unsw.EDU.AU>
Cc: Andrew Morton <akpm@osdl.org>,
	David Singleton <dsingleton@mvista.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Lee.Schermerhorn@hp.com
Subject: Re: new procfs memory analysis feature
Date: Fri, 08 Dec 2006 13:46:10 -0800	[thread overview]
Message-ID: <4579DD22.70609@goop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0612081716440.28861@weill.orchestra.cse.unsw.EDU.AU>

Paul Cameron Davies wrote:
> The PTI gathers all the open coded iterators togethers into one place,
> which would be a good precursor to providing generic iterators for
> non performance critical iterations.
>
> We are completing the updating/enhancements to this PTI for the latest
> kernel, to be released just prior to LCA.  This PTI is benchmarking
> well. We also plan to release the experimental guarded page table
> (GPT) running under this PTI.

I looked at implementing linear pagetable mappings for x86 as a way of
getting rid of CONFIG_HIGHPTE, and to make pagetable manipulations
generally more efficient.  I gave up on it after a while because all the
existing pagetable accessors are not suitable for a linear pagetable,
and I didn't want to have to introduce a pile of new pagetable
interfaces.  Would the PTI interface be helpful for this?

Thanks,
    J

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

  reply	other threads:[~2006-12-08 21:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07 22:09 new procfs memory analysis feature David Singleton
2006-12-07 22:36 ` Andrew Morton
2006-12-07 22:36   ` Andrew Morton
2006-12-08  0:30   ` david singleton
2006-12-08  0:30     ` david singleton
2006-12-08  1:07   ` david singleton
2006-12-08  1:46     ` Andrew Morton
2006-12-08  1:46       ` Andrew Morton
2006-12-08  1:53       ` david singleton
2006-12-08  1:53         ` david singleton
2006-12-08  6:21   ` Paul Cameron Davies
2006-12-08  6:21     ` Paul Cameron Davies
2006-12-08 21:46     ` Jeremy Fitzhardinge [this message]
2006-12-08 21:46       ` Jeremy Fitzhardinge
2006-12-11  2:19       ` Paul Cameron Davies
2006-12-11  2:19         ` Paul Cameron Davies
  -- strict thread matches above, loose matches on Subject: below --
2006-12-11  8:13 Albert Cahalan
2006-12-11  8:13 ` Albert Cahalan
2006-12-12  1:15 ` Joe Green
2006-12-12  1:15   ` Joe Green

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=4579DD22.70609@goop.org \
    --to=jeremy@goop.org \
    --cc=Lee.Schermerhorn@hp.com \
    --cc=akpm@osdl.org \
    --cc=dsingleton@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pauld@cse.unsw.EDU.AU \
    /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.