From: "Paul Menage" <menage@google.com>
To: balbir@linux.vnet.ibm.com
Cc: Pavel Emelianov <xemul@openvz.org>,
Hugh Dickins <hugh@veritas.com>,
Sudhir Kumar <skumar@linux.vnet.ibm.com>,
YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
lizf@cn.fujitsu.com, linux-kernel@vger.kernel.org,
taka@valinux.co.jp, linux-mm@kvack.org,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [RFC][-mm] Add an owner to the mm_struct (v4)
Date: Wed, 2 Apr 2008 12:53:47 -0700 [thread overview]
Message-ID: <6599ad830804021253y6bf3b37y9bf1167b63c32e70@mail.gmail.com> (raw)
In-Reply-To: <47F3D62E.4070808@linux.vnet.ibm.com>
On Wed, Apr 2, 2008 at 11:53 AM, Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
>
> So far I've heard no objections or seen any review suggestions. Paul if you are
> OK with this patch, I'll ask Andrew to include it in -mm.
My only thoughts were:
- I think I'd still prefer CONFIG_MM_OWNER to be auto-selected rather
than manually configured, but it's not a huge deal either way.
- in theory I think we should goto retry if we get to the end of
mm_update_next_owner() without finding any other owner. Otherwise we
could miss another user if we race with one process forking a new
child and then exiting?
- I was looking through the exit code trying to convince myself that
current is still on the tasklist until after it makes this call. If it
isn't then we could have trouble finding the new owner. But I can't
figure out for sure exactly at what point we come off the tasklist.
- I think we only need the cgroup callback in the event that
current->cgroups != new_owner->cgroups. (Hmm, have we already been
moved back to the root cgroup by this point? If so, then we'll have no
way to know which cgruop to unaccount from).
Paul
>
> People waiting on this patch
>
> 1. Pekka Enberg for revoke* syscalls
> 2. Serge Hallyn for swap namespaces
> 3. Myself to implement the rlimit controller for cgroups
>
>
>
> --
> Warm Regards,
> Balbir Singh
> Linux Technology Center
> IBM, ISTL
>
next prev parent reply other threads:[~2008-04-02 19:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 12:43 Balbir Singh
2008-04-01 16:00 ` Pekka Enberg
2008-04-01 16:15 ` Balbir Singh
2008-04-02 0:31 ` KAMEZAWA Hiroyuki
2008-04-02 3:25 ` Balbir Singh
2008-04-02 4:53 ` KAMEZAWA Hiroyuki
2008-04-02 6:40 ` Balbir Singh
2008-04-02 19:27 ` Paul Menage
2008-04-02 18:53 ` Balbir Singh
2008-04-02 19:53 ` Paul Menage [this message]
2008-04-03 4:05 ` Balbir Singh
2008-04-03 4:10 ` Paul Menage
2008-04-03 4:32 ` Balbir Singh
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=6599ad830804021253y6bf3b37y9bf1167b63c32e70@mail.gmail.com \
--to=menage@google.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=rientjes@google.com \
--cc=skumar@linux.vnet.ibm.com \
--cc=taka@valinux.co.jp \
--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