From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Paul Menage <menage@google.com>,
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: Tue, 01 Apr 2008 21:45:09 +0530 [thread overview]
Message-ID: <47F25F8D.7080102@linux.vnet.ibm.com> (raw)
In-Reply-To: <84144f020804010900s5335988ai58546874a6a2f8bd@mail.gmail.com>
Pekka Enberg wrote:
> Hi,
>
> On Tue, Apr 1, 2008 at 3:43 PM, Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
>> @@ -227,8 +227,9 @@ struct mm_struct {
>> /* aio bits */
>> rwlock_t ioctx_list_lock;
>> struct kioctx *ioctx_list;
>> -#ifdef CONFIG_CGROUP_MEM_RES_CTLR
>> - struct mem_cgroup *mem_cgroup;
>> +#ifdef CONFIG_MM_OWNER
>> + struct task_struct *owner; /* The thread group leader that */
>> + /* owns the mm_struct. */
>> #endif
>
> Yes, please. This is useful for the revokeat() patches as well. I
> currently need a big ugly loop to scan each task so I can break COW of
> private pages.
Hi, Pekka,
It's good to know that this will be useful. I think understand your use case of
having to walk the entire tasklist to break COW of private pages, having the
owner information right in the mm_struct is definitely useful.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
next prev parent reply other threads:[~2008-04-01 16:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 12:43 [RFC][-mm] Add an owner to the mm_struct (v4) Balbir Singh
2008-04-01 12:43 ` Balbir Singh
2008-04-01 16:00 ` Pekka Enberg
2008-04-01 16:15 ` Balbir Singh [this message]
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
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=47F25F8D.7080102@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--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=menage@google.com \
--cc=penberg@cs.helsinki.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.