From: Andrea Arcangeli <andrea@suse.de>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: Arjan van de Ven <arjanv@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
gerrit@us.ibm.com
Subject: Re: Backport of Ingo/Arjan highpte to 2.4.18 (+O1 scheduler)
Date: Tue, 26 Mar 2002 19:18:14 +0100 [thread overview]
Message-ID: <20020326191814.F13052@dualathlon.random> (raw)
In-Reply-To: <242250000.1016752254@flay> <20020326180841.C13052@dualathlon.random> <49720000.1017165747@flay>
On Tue, Mar 26, 2002 at 10:02:27AM -0800, Martin J. Bligh wrote:
>
> > First, your backport is clearly broken because it will oops in
> > copy_one_pte if the alloc_one_pte_map fails.
>
> That doesn't suprise me ... I did a quick backport without staring
> at the code too much, just so I could get some testing number to
> see what the difference in performance would be. Arjan is doing
> a proper backport to 2.4, and he obviously knows this patch far
I need persistent kmaps for the pagetables, and also the quicklists, so
I'm not excited to integrate a 2.4 backport of an halfway solution that
isn't optimal for 2.5 either (plus at the moment it's buggy and
incidentally the right fix is to add the persistent kmaps in 2.5 too, go
figure).
Andrea
next prev parent reply other threads:[~2002-03-26 18:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 23:10 Backport of Ingo/Arjan highpte to 2.4.18 (+O1 scheduler) Martin J. Bligh
2002-03-21 23:20 ` Martin J. Bligh
2002-03-26 17:08 ` Andrea Arcangeli
2002-03-26 18:02 ` Martin J. Bligh
2002-03-26 18:18 ` Andrea Arcangeli [this message]
2002-03-28 22:48 ` Testing of Ingo/Arjan highpte on 16-way NUMA-Q Martin J. Bligh
2002-03-29 22:49 ` Backport of Ingo/Arjan highpte to 2.4.18 (+O1 scheduler) Martin J. Bligh
2002-03-30 19:44 ` Andrea Arcangeli
2002-03-31 14:51 ` Andrea Arcangeli
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=20020326191814.F13052@dualathlon.random \
--to=andrea@suse.de \
--cc=Martin.Bligh@us.ibm.com \
--cc=arjanv@redhat.com \
--cc=gerrit@us.ibm.com \
--cc=linux-kernel@vger.kernel.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