All of lore.kernel.org
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@in.ibm.com>
To: "Patrick.Le-Dot" <Patrick.Le-Dot@bull.net>
Cc: dev@openvz.org, ckrm-tech@lists.sourceforge.net,
	haveblue@us.ibm.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, rohitseth@google.com
Subject: Re: [ckrm-tech] [RFC][PATCH 5/8] RSS controller task migration	support
Date: Wed, 15 Nov 2006 22:07:25 +0530	[thread overview]
Message-ID: <455B4245.8000309@in.ibm.com> (raw)
In-Reply-To: <20061115115937.B0A851B6A2@openx4.frec.bull.fr>

Patrick.Le-Dot wrote:
> Hi Balbir,
> 
> The get_task_mm()/mmput(mm) usage is not correct.
> With CONFIG_DEBUG_SPINLOCK_SLEEP=y :
> 
> BUG: sleeping function called from invalid context at kernel/fork.c:390
> in_atomic():1, irqs_disabled():0
>  [<c0116620>] __might_sleep+0x97/0x9c
>  [<c0116a2e>] mmput+0x15/0x8b
>  [<c01582f6>] install_arg_page+0x72/0xa9
>  [<c01584b1>] setup_arg_pages+0x184/0x1a5
>  ...
> 
> BUG: sleeping function called from invalid context at kernel/fork.c:390
> in_atomic():1, irqs_disabled():0
>  [<c0116620>] __might_sleep+0x97/0x9c
>  [<c0116a2e>] mmput+0x15/0x8b
>  [<c01468ee>] do_no_page+0x255/0x2bd
>  [<c0146b8d>] __handle_mm_fault+0xed/0x1ef
>  [<c0111884>] do_page_fault+0x247/0x506
>  [<c011163d>] do_page_fault+0x0/0x506
>  [<c0348f99>] error_code+0x39/0x40
> 
> 
> current->mm seems to be enough here.

Excellent, thanks for catching this!

> 
> 
> 
> In patch4, memctlr_dec_rss(page, mm) should be memctlr_dec_rss(page)
> to compile correctly.
> 
> and in patch0 :
>> 4. Disable cpuset's (to simply assignment of tasks to resource groups)
>>         cd /container
>>         echo 0 > cpuset_enabled
> 
> should be :
>         echo 0 > cpuacct_enabled
> 
> Note : cpuacct_enabled is 0 by default.
> 

Thanks for pointing this out.

> 
> Now the big question : to implement guarantee, the LRU needs to know
> if a page can be removed from memory or not.
> Any ideas to do that without any change in the struct page ?
> 

For implementing guarantees, we can use limits. Please see
http://wiki.openvz.org/Containers/Guarantees_for_resources.


Thanks for the feedback!

-- 

	Balbir Singh,
	Linux Technology Center,
	IBM Software Labs

WARNING: multiple messages have this Message-ID (diff)
From: Balbir Singh <balbir@in.ibm.com>
To: "Patrick.Le-Dot" <Patrick.Le-Dot@bull.net>
Cc: dev@openvz.org, ckrm-tech@lists.sourceforge.net,
	haveblue@us.ibm.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, rohitseth@google.com
Subject: Re: [ckrm-tech] [RFC][PATCH 5/8] RSS controller task migration	support
Date: Wed, 15 Nov 2006 22:07:25 +0530	[thread overview]
Message-ID: <455B4245.8000309@in.ibm.com> (raw)
In-Reply-To: <20061115115937.B0A851B6A2@openx4.frec.bull.fr>

Patrick.Le-Dot wrote:
> Hi Balbir,
> 
> The get_task_mm()/mmput(mm) usage is not correct.
> With CONFIG_DEBUG_SPINLOCK_SLEEP=y :
> 
> BUG: sleeping function called from invalid context at kernel/fork.c:390
> in_atomic():1, irqs_disabled():0
>  [<c0116620>] __might_sleep+0x97/0x9c
>  [<c0116a2e>] mmput+0x15/0x8b
>  [<c01582f6>] install_arg_page+0x72/0xa9
>  [<c01584b1>] setup_arg_pages+0x184/0x1a5
>  ...
> 
> BUG: sleeping function called from invalid context at kernel/fork.c:390
> in_atomic():1, irqs_disabled():0
>  [<c0116620>] __might_sleep+0x97/0x9c
>  [<c0116a2e>] mmput+0x15/0x8b
>  [<c01468ee>] do_no_page+0x255/0x2bd
>  [<c0146b8d>] __handle_mm_fault+0xed/0x1ef
>  [<c0111884>] do_page_fault+0x247/0x506
>  [<c011163d>] do_page_fault+0x0/0x506
>  [<c0348f99>] error_code+0x39/0x40
> 
> 
> current->mm seems to be enough here.

Excellent, thanks for catching this!

> 
> 
> 
> In patch4, memctlr_dec_rss(page, mm) should be memctlr_dec_rss(page)
> to compile correctly.
> 
> and in patch0 :
>> 4. Disable cpuset's (to simply assignment of tasks to resource groups)
>>         cd /container
>>         echo 0 > cpuset_enabled
> 
> should be :
>         echo 0 > cpuacct_enabled
> 
> Note : cpuacct_enabled is 0 by default.
> 

Thanks for pointing this out.

> 
> Now the big question : to implement guarantee, the LRU needs to know
> if a page can be removed from memory or not.
> Any ideas to do that without any change in the struct page ?
> 

For implementing guarantees, we can use limits. Please see
http://wiki.openvz.org/Containers/Guarantees_for_resources.


Thanks for the feedback!

-- 

	Balbir Singh,
	Linux Technology Center,
	IBM Software Labs

--
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>

  reply	other threads:[~2006-11-15 16:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15 11:59 [RFC][PATCH 5/8] RSS controller task migration support Patrick.Le-Dot
2006-11-15 11:59 ` Patrick.Le-Dot
2006-11-15 16:37 ` Balbir Singh [this message]
2006-11-15 16:37   ` [ckrm-tech] " Balbir Singh
  -- strict thread matches above, loose matches on Subject: below --
2006-11-17 13:25 Patrick.Le-Dot
2006-11-17 13:25 ` Patrick.Le-Dot
2006-11-17 14:05 ` Alan
2006-11-17 14:05   ` Alan
2006-11-17 16:34 ` Balbir Singh
2006-11-17 16:34   ` Balbir Singh
2006-11-17 14:42 Patrick.Le-Dot
2006-11-17 14:42 ` Patrick.Le-Dot

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=455B4245.8000309@in.ibm.com \
    --to=balbir@in.ibm.com \
    --cc=Patrick.Le-Dot@bull.net \
    --cc=ckrm-tech@lists.sourceforge.net \
    --cc=dev@openvz.org \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rohitseth@google.com \
    /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.