From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, skumar@linux.vnet.ibm.com,
yamamoto@valinux.co.jp, menage@google.com, lizf@cn.fujitsu.com,
linux-kernel@vger.kernel.org, xemul@openvz.org,
kamezawa.hiroyu@jp.fujitsu.com, mingo@elte.hu
Subject: Re: [-mm][PATCH 4/4] Add memrlimit controller accounting and control (v4)
Date: Fri, 19 Sep 2008 14:28:13 -0700 [thread overview]
Message-ID: <48D4196D.6050003@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080919131405.1a95c491.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Thu, 18 Sep 2008 23:38:23 -0700
> Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
>
>> * Andrew Morton <akpm@linux-foundation.org> [2008-09-18 13:54:30]:
>>
>>> On Wed, 14 May 2008 18:39:51 +0530
>>> Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
>>>
>>>> This patch adds support for accounting and control of virtual address space
>>>> limits.
>>>
>>> Large changes in linux-next's arch/x86/kernel/ptrace.c caused damage to
>>> the memrlimit patches.
>>>
>>> I decided to retain the patches because it looks repairable. The
>>> problem is this reject from
>>> memrlimit-add-memrlimit-controller-accounting-and-control.patch:
>>>
>> Andrew,
>>
>> I could not apply mmotm to linux-next (both downloaded right now).
>
> mmotm includes linux-next.patch. mmotm is based upon the most recent
> 2.6.x-rcy.
>
Thanks for the info
[snip]
> OK, we'll give it a shot, thanks.
>
Thanks!
--
Balbir
--
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:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2008-09-19 21:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 13:09 [-mm][PATCH 0/4] Add memrlimit controller (v4) Balbir Singh
2008-05-14 13:09 ` [-mm][PATCH 1/4] Add memrlimit controller documentation (v4) Balbir Singh
2008-05-15 1:20 ` Li Zefan
2008-05-15 18:22 ` Avi Kivity
2008-05-15 18:39 ` Balbir Singh
2008-05-14 13:09 ` [-mm][PATCH 2/4] Setup the memrlimit controller (v4) Balbir Singh
2008-05-14 13:29 ` Pavel Emelyanov
2008-05-14 13:09 ` [-mm][PATCH 3/4] cgroup mm owner callback changes to add task info (v4) Balbir Singh
2008-05-14 13:09 ` [-mm][PATCH 4/4] Add memrlimit controller accounting and control (v4) Balbir Singh
2008-05-14 13:25 ` Balbir Singh
2008-05-15 2:25 ` Paul Menage
2008-05-15 6:17 ` Balbir Singh
2008-05-15 6:55 ` Paul Menage
2008-05-15 7:03 ` Balbir Singh
2008-05-15 7:39 ` Paul Menage
2008-05-15 8:25 ` Balbir Singh
2008-05-15 15:28 ` Paul Menage
2008-05-15 17:01 ` Balbir Singh
2008-05-17 20:15 ` Balbir Singh
2008-05-17 20:17 ` Balbir Singh
2008-05-14 13:32 ` Pavel Emelyanov
2008-05-14 19:39 ` Balbir Singh
2008-09-18 20:54 ` Andrew Morton
2008-09-18 23:55 ` Balbir Singh
2008-09-19 6:38 ` Balbir Singh
2008-09-19 20:14 ` Andrew Morton
2008-09-19 21:28 ` Balbir Singh [this message]
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=48D4196D.6050003@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=mingo@elte.hu \
--cc=skumar@linux.vnet.ibm.com \
--cc=xemul@openvz.org \
--cc=yamamoto@valinux.co.jp \
/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;
as well as URLs for NNTP newsgroup(s).