From: "Martin J. Bligh" <mbligh@aracnet.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@digeo.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.73-mm2
Date: Sat, 28 Jun 2003 20:07:06 -0700 [thread overview]
Message-ID: <4160000.1056856024@[10.10.2.4]> (raw)
In-Reply-To: <20030629021809.GA26348@holomorphy.com>
--William Lee Irwin III <wli@holomorphy.com> wrote (on Saturday, June 28, 2003 19:18:09 -0700):
> On Sat, Jun 28, 2003 at 05:34:05PM -0700, Martin J. Bligh wrote:
>> Last time I measured it, it had about a 10% overhead in kernel time.
>> Seems like a good thing to keep as an option to me. Bill said he
>> had some other code to alleviate the overhead, but I don't think
>> it's merged ... I'd rather see UKVA (permanently map the pagetables
>> on a per-process basis) merged before it becomes "not an option" -
>> that gets rid of all the kmapping.
>
> There are several orthogonal things going on here. One is dropping the
> hooks in the right places to get various concrete tasks done. Another
> is general resource scalability vs. raw overhead tradeoffs. The last
> one is gathering a wide enough repertoire of core hooks that arches can
> use "advanced" techniques like recursive pagetables when they require
> various kinds of intervention by the kernel to use.
>
> This is just another set of hooks we'll need for our end goal, with a
> fully functional implementation. It has direct applications and is
> completely usable now for resource scalability albeit with some
> overhead. Things are all headed in the appropriate directions; the
> hooks do not conflict with and do not require any core modifications
> whatsoever in order to use in combination with recursive pagetables;
> they can simply recover information from already-available places and
> transparently replace the highpmd and highpte arch code.
>
> I can work directly with Dave to arrange a proper demonstration of this
> (i.e. fully functional implementation) if need be. I've largely avoided
> interceding in recursive pagetable mechanics in order not to duplicate
> work.
Right, I'm not against what you're doing - I'm totally for it. My only
concern was that whilst it has some overhead, it should stay as a config
option (which you did). That lets people make the call of overhead vs
resource scaling.
Your patch is fine - just the talk of removing the config option scared
me ;-)
M.
next prev parent reply other threads:[~2003-06-29 2:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-28 3:21 2.5.73-mm2 Andrew Morton
2003-06-28 8:56 ` 2.5.73-mm2 William Lee Irwin III
2003-06-28 15:54 ` 2.5.73-mm2 William Lee Irwin III
2003-06-28 16:08 ` 2.5.73-mm2 Christoph Hellwig
2003-06-28 20:49 ` 2.5.73-mm2 William Lee Irwin III
2003-06-29 0:34 ` 2.5.73-mm2 Martin J. Bligh
2003-06-29 2:18 ` 2.5.73-mm2 William Lee Irwin III
2003-06-29 3:07 ` Martin J. Bligh [this message]
2003-06-28 23:00 ` 2.5.73-mm2 Andrew Morton
2003-06-28 23:11 ` 2.5.73-mm2 William Lee Irwin III
2003-06-29 12:45 ` 2.5.73-mm2 Zwane Mwaikambo
2003-07-02 3:11 ` 2.5.73-mm2 William Lee Irwin III
2003-06-29 19:04 ` [patch] 2.5.73-mm2: let CONFIG_TC35815 depend on CONFIG_TOSHIBA_JMR3927 Adrian Bunk
2003-06-29 21:04 ` Ralf Baechle
2003-07-01 0:39 ` 2.5.73-mm2 William Lee Irwin III
2003-07-01 2:14 ` 2.5.73-mm2 Andrew Morton
2003-07-01 2:46 ` 2.5.73-mm2 William Lee Irwin III
2003-07-01 10:46 ` 2.5.73-mm2 Hugh Dickins
2003-07-01 10:51 ` 2.5.73-mm2 William Lee Irwin III
2003-07-01 11:08 ` 2.5.73-mm2 Hugh Dickins
2003-07-01 11:08 ` 2.5.73-mm2 William Lee Irwin III
2003-07-01 12:39 ` 2.5.73-mm2 Nikita Danilov
2003-07-01 5:56 ` 2.5.73-mm2 William Lee Irwin III
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='4160000.1056856024@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=akpm@digeo.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=wli@holomorphy.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;
as well as URLs for NNTP newsgroup(s).