From: Darren Williams <dsw@gelato.unsw.edu.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] long format VHPT
Date: Mon, 29 Sep 2003 23:48:51 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106487935616561@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106453902218848@msgid-missing>
Hi Arun
These are useful suggestions and we will need a solution that covers all
possible scenarios for the page table walker, I have just begun looking
at the Ia64 code and so my responses may be slow until I get my head
around it. One question I do have is that if we are initialising vhpt
in do_boot_cpu() are we only talking about SMP machines here, what
about UNI processor machines?
Darren
On Mon, 29 Sep 2003, Arun Sharma wrote:
> Chen, Kenneth W wrote:
> >I did some hacking over the weekend. VHPT allocation can be done
> >from boot processor in function do_boot_cpu() before waking up
> >secondary CPUs. Allocation can be easily made numa friendly by
> >calling alloc_pages_node (didn't bother to do that for now).
>
> I was thinking of the hot-plug CPU case, where the allocation has to be
> done on the newly added CPU anyway.
>
> -Arun
--------------------------------------------------
Darren Williams <dsw@gelato.unsw.edu.au>
Gelato@UNSW <www.gelato.unsw.edu.au>
--------------------------------------------------
next prev parent reply other threads:[~2003-09-29 23:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 1:12 [PATCH] long format VHPT Darren Williams
2003-09-26 22:24 ` Arun Sharma
2003-09-26 23:42 ` Darren Williams
2003-09-28 23:44 ` Chen, Kenneth W
2003-09-29 17:43 ` Arun Sharma
2003-09-29 23:48 ` Darren Williams [this message]
2003-09-30 18:25 ` Arun Sharma
2003-10-01 0:58 ` Arun Sharma
2003-10-02 1:30 ` Arun Sharma
2003-10-02 1:51 ` Peter Chubb
2003-10-02 2:10 ` Matt Chapman
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=marc-linux-ia64-106487935616561@msgid-missing \
--to=dsw@gelato.unsw.edu.au \
--cc=linux-ia64@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.