From: Paul Jackson <pj@sgi.com>
To: akpm@osdl.org
Cc: Simon.Derr@bull.net, ak@suse.de, clameter@sgi.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] cpuset: rebind numa vma mempolicy
Date: Sun, 6 Nov 2005 22:10:55 -0800 [thread overview]
Message-ID: <20051106221055.2c8760d8.pj@sgi.com> (raw)
In-Reply-To: <20051104053120.549.73652.sendpatchset@jackhammer.engr.sgi.com>
Andrew - please remove these two patches from *-mm for now. I need to
think more about the mmap_sem locking issues. The questions you asked
were good ones - thanks. My answers so far suck.
[PATCH 2/5] cpuset: rebind numa vma mempolicy
[PATCH 6/5] cpuset: rebind numa vma mempolicy fix
aka
cpuset-rebind-numa-vma-mempolicy.patch
cpuset-rebind-numa-vma-mempolicy-fix.patch
So far as I can tell, nothing is actually broken with this pair of
patches. My cpuset function and stress tests still passed. But they
are too hacky^W non-deterministic.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2005-11-07 6:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 5:31 [PATCH 1/5] cpuset: better bitmap remap defaults Paul Jackson
2005-11-04 5:31 ` [PATCH 2/5] cpuset: rebind numa vma mempolicy Paul Jackson
2005-11-07 6:10 ` Paul Jackson [this message]
2005-11-04 5:31 ` [PATCH 3/5] cpuset: change marker for relative numbering Paul Jackson
2005-11-05 7:08 ` Andrew Morton
2005-11-06 10:04 ` Paul Jackson
2005-11-06 20:57 ` Andrew Morton
2005-11-06 22:49 ` Paul Jackson
2005-11-04 5:31 ` [PATCH 4/5] cpuset: mempolicy one more nodemask conversion Paul Jackson
2005-11-04 5:31 ` [PATCH 5/5] cpuset: memory reclaim rate meter Paul Jackson
2005-11-05 7:13 ` Andrew Morton
2005-11-05 7:34 ` Paul Jackson
2005-11-05 7:43 ` Paul Jackson
2005-11-05 7:27 ` Paul Jackson
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=20051106221055.2c8760d8.pj@sgi.com \
--to=pj@sgi.com \
--cc=Simon.Derr@bull.net \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=clameter@sgi.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