linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Dave McCracken <dmccr@us.ibm.com>, Bill Davidsen <davidsen@tmr.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Andrew Morton <akpm@digeo.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [PATCH 2.5.43-mm2] New shared page table patch
Date: Thu, 24 Oct 2002 07:51:46 -0700	[thread overview]
Message-ID: <2834413140.1035445904@[10.10.2.3]> (raw)
In-Reply-To: <9100000.1035470286@baldur.austin.ibm.com>

>>> Another thought, how does this play with NUMA systems? I don't have the
>>> problem, but presumably there are implications.
>> 
>> At some point we'll probably only want one shared set per node.
>> Gets tricky when you migrate processes across nodes though - will
>> need more thought
> 
> Page tables can only be shared when they're pointing to the same 
> data pages anyway, so I think it's just part of the larger problem 
> of node-local memory.

Yes, same problem as text replication. You're right, it's probably not 
worth solving otherwise - too small a percentage of the real problem.

M.

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

  reply	other threads:[~2002-10-24 14:51 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-18 23:06 Dave McCracken
2002-10-19  1:32 ` Ed Tomlinson
2002-10-19 19:17 ` Bill Davidsen
2002-10-19 19:36   ` Dave McCracken
2002-10-20  4:20     ` Eric W. Biederman
2002-10-20  6:18   ` Martin J. Bligh
2002-10-21 14:55     ` Eric W. Biederman
2002-10-21 15:21       ` Martin J. Bligh
2002-10-22  3:54         ` Eric W. Biederman
2002-10-22  5:55           ` Martin J. Bligh
2002-10-22 16:09             ` Rik van Riel
2002-10-22 16:14               ` Martin J. Bligh
2002-10-22 18:06                 ` Bill Davidsen
2002-10-22 19:02                   ` Martin J. Bligh
2002-10-22 19:21                     ` Dave McCracken
2002-10-24 10:50                       ` Bill Davidsen
2002-10-24 14:22                         ` Martin J. Bligh
2002-10-24 14:38                           ` Dave McCracken
2002-10-24 14:51                             ` Martin J. Bligh [this message]
2002-10-25 17:31                           ` Bill Davidsen
2002-10-24 10:42                     ` Bill Davidsen
2002-10-22 17:19               ` Benjamin LaHaise
2002-10-22 17:36                 ` Martin J. Bligh
2002-10-22 17:45                   ` Benjamin LaHaise
2002-10-22 17:56                     ` Andrew Morton
2002-10-22 18:01                       ` Benjamin LaHaise
2002-10-22 19:03                         ` Martin J. Bligh
2002-10-22 20:23                           ` Alan Cox
2002-10-22 21:33                             ` Gerrit Huizenga
2002-10-22 18:22                     ` Alan Cox
2002-10-22 18:47                       ` Gerrit Huizenga
2002-10-22 18:55                         ` Benjamin LaHaise
2002-10-22 19:27                           ` Gerrit Huizenga
2002-10-22 19:29                             ` Benjamin LaHaise
2002-10-22 19:56                             ` Arjan van de Ven
2002-10-22 14:26           ` Rik van Riel
2002-10-22 17:09             ` Andrew Morton
2002-10-22 17:15               ` Rik van Riel
2002-10-22 18:36                 ` Dave McCracken
2002-10-22 18:49                   ` Andrew Morton
2002-10-22 19:06                     ` Gerrit Huizenga
2002-10-22 19:29                       ` Dave McCracken
2002-10-22 19:11                   ` Ulrich Drepper
2002-10-22 19:29                     ` Gerrit Huizenga
2002-10-22 18:45               ` Gerrit Huizenga
2002-10-22 17:54             ` Bill Davidsen

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='2834413140.1035445904@[10.10.2.3]' \
    --to=mbligh@aracnet.com \
    --cc=akpm@digeo.com \
    --cc=davidsen@tmr.com \
    --cc=dmccr@us.ibm.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@conectiva.com.br \
    /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