[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47F25F8D.7080102@linux.vnet.ibm.com>
Date: Tue, 01 Apr 2008 21:45:09 +0530
From: Balbir Singh <balbir@...ux.vnet.ibm.com>
To: Pekka Enberg <penberg@...helsinki.fi>
CC: Paul Menage <menage@...gle.com>,
Pavel Emelianov <xemul@...nvz.org>,
Hugh Dickins <hugh@...itas.com>,
Sudhir Kumar <skumar@...ux.vnet.ibm.com>,
YAMAMOTO Takashi <yamamoto@...inux.co.jp>, lizf@...fujitsu.com,
linux-kernel@...r.kernel.org, taka@...inux.co.jp,
linux-mm@...ck.org, David Rientjes <rientjes@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Subject: Re: [RFC][-mm] Add an owner to the mm_struct (v4)
Pekka Enberg wrote:
> Hi,
>
> On Tue, Apr 1, 2008 at 3:43 PM, Balbir Singh <balbir@...ux.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists