All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Andrea Arcangeli <andrea@suse.de>, Arjan van de Ven <arjanv@redhat.com>
Cc: 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 10:02:27 -0800	[thread overview]
Message-ID: <49720000.1017165747@flay> (raw)
In-Reply-To: <20020326180841.C13052@dualathlon.random>


> 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
better than I, so hopefully he'll address this ;-)

Thanks for pointing this out.

> ....

The bulk of the rest of this will take me a while to think about ;-)

Thanks,

M.

PS. The backport of the 2.5 highpte stuff works fine for me in limited
touch-testing, but I don't have it playing with the discontigmem stuff
yet, so I can't give you any numbers at the moment ...



  reply	other threads:[~2002-03-26 18:03 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 [this message]
2002-03-26 18:18     ` Andrea Arcangeli
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=49720000.1017165747@flay \
    --to=martin.bligh@us.ibm.com \
    --cc=andrea@suse.de \
    --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 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.