From: Paul Jackson <pj@sgi.com>
To: Robin Holt <holt@sgi.com>
Cc: raybry@sgi.com, linux-mm@kvack.org, ak@muc.de,
haveblue@us.ibm.com, marcello@cyclades.com,
stevel@mwwireless.net, peterc@gelato.unsw.edu.au
Subject: Re: manual page migration -- issue list
Date: Tue, 15 Feb 2005 20:24:34 -0800 [thread overview]
Message-ID: <20050215202434.63d349ed.pj@sgi.com> (raw)
In-Reply-To: <20050216020138.GC28354@lnx-holt.americas.sgi.com>
Robin wrote:
> Overlapping nodes with the above will make
> a complete mess of your memory placement.
I agree we don't want to overlap nodes.
I don't yet understand why my simple (simplistic?)
version of this system call leads us to overlapped
nodes.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373, 1.925.600.0401
--
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/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-02-16 4:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 23:52 Ray Bryant
2005-02-16 0:09 ` Paul Jackson
2005-02-16 0:28 ` Ray Bryant
2005-02-16 0:51 ` Paul Jackson
2005-02-16 1:17 ` Paul Jackson
2005-02-16 2:01 ` Robin Holt
2005-02-16 4:04 ` Ray Bryant
2005-02-16 4:28 ` Paul Jackson
2005-02-16 4:24 ` Paul Jackson [this message]
2005-02-16 3:55 ` Ray Bryant
2005-02-16 1:56 ` Robin Holt
2005-02-16 4:22 ` Paul Jackson
2005-02-16 9:20 ` Robin Holt
2005-02-16 10:20 ` Paul Jackson
2005-02-16 11:30 ` Robin Holt
2005-02-16 15:45 ` Paul Jackson
2005-02-16 16:08 ` Robin Holt
2005-02-16 19:23 ` Paul Jackson
2005-02-16 19:56 ` Robin Holt
2005-02-16 23:08 ` Ray Bryant
2005-02-16 23:05 ` Ray Bryant
2005-02-17 0:28 ` Paul Jackson
2005-02-16 1:41 ` Paul Jackson
2005-02-16 3:56 ` Ray Bryant
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=20050215202434.63d349ed.pj@sgi.com \
--to=pj@sgi.com \
--cc=ak@muc.de \
--cc=haveblue@us.ibm.com \
--cc=holt@sgi.com \
--cc=linux-mm@kvack.org \
--cc=marcello@cyclades.com \
--cc=peterc@gelato.unsw.edu.au \
--cc=raybry@sgi.com \
--cc=stevel@mwwireless.net \
/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