From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Cedric Le Goater <clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
Cc: Kir Kolyshkin <kir-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>,
Linux Containers
<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org
Subject: Re: [Devel] OLS paper topics
Date: Wed, 30 Jan 2008 09:48:01 -0600 [thread overview]
Message-ID: <20080130154801.GC1206@sergelap.austin.ibm.com> (raw)
In-Reply-To: <47A07430.3000600-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
Quoting Cedric Le Goater (clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org):
>
>> Why is that a conflict w.r.t resource management, isn't that more of a
>> cgroup
>> feature - task migration. We need task migration for resource management,
>> but
>> task migration is a system administrator/management function. I don't see
>> the
>> conflict, but may be I am missing something very obvious.
>
> This is something we may want to dig. from a checkpoint/restart POV, a
> 'container' acts a whole and you don't want tasks to be migrated from a
> container to another. They have to share the same container properties.
> it might be possible to solve that issue from user space or by making sure
> a set of cgroups are dedicated to a container.
This is certainly a good topic for the mini-summit.
The simple answer of course is you create a container for the virtual
server, then create containers within those around the applications you
want to checkpoint. But depending on logistics (i.e. per-container
swapfiles) this could get complicated.
-serge
next prev parent reply other threads:[~2008-01-30 15:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 19:57 OLS paper topics Serge E. Hallyn
[not found] ` <20080123195736.GA7823-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
2008-01-24 22:05 ` [Devel] " Kir Kolyshkin
[not found] ` <47990BAB.4050106-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-01-24 22:50 ` Serge E. Hallyn
[not found] ` <20080124225002.GC13819-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
2008-01-25 0:13 ` Kir Kolyshkin
2008-01-30 8:50 ` Kir Kolyshkin
[not found] ` <47A03A73.6070408-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-01-30 8:58 ` Balbir Singh
[not found] ` <47A03C25.8030205-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2008-01-30 9:53 ` Cedric Le Goater
[not found] ` <47A04916.50904-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-01-30 9:59 ` Balbir Singh
[not found] ` <47A04A7A.9030701-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2008-01-30 12:57 ` Cedric Le Goater
[not found] ` <47A07430.3000600-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-01-30 15:48 ` Serge E. Hallyn [this message]
2008-01-30 15:52 ` Serge E. Hallyn
[not found] ` <20080130155220.GD1206-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
2008-01-30 16:54 ` Balbir Singh
2008-01-30 10:43 ` Dhaval Giani
[not found] ` <20080130104336.GD3862-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2008-01-30 15:40 ` Serge E. Hallyn
[not found] ` <20080130154043.GB1206-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
2008-01-31 7:49 ` Dhaval Giani
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=20080130154801.GC1206@sergelap.austin.ibm.com \
--to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=kir-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
/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