From: Matt Helsley <matthltc@us.ibm.com>
To: Cyrill Gorcunov <gorcunov@openvz.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Pavel Emelyanov <xemul@parallels.com>,
James Bottomley <jbottomley@parallels.com>,
ebiederm@xmission.com, tj@kernel.org, skinsbursky@openvz.org
Subject: Re: [rfc v2 0/7] procfs fdinfo extension v2
Date: Thu, 24 May 2012 11:01:21 -0700 [thread overview]
Message-ID: <20120524180121.GK798@count0.beaverton.ibm.com> (raw)
In-Reply-To: <20120523102541.382837149@openvz.org>
On Wed, May 23, 2012 at 02:25:41PM +0400, Cyrill Gorcunov wrote:
<snip>
> - finally it would be great to have ability to attach tasks to
> frozen tasks cgroup to thaw them at one moment (the preliminary
> patch I've proposed pretty long ago, but Tejun was modifying cgroups
> code and asked to wait until 3.4 is release, so I didn't check
> the current status of task cgroups at moment, I've it in my todo list)
This still strikes me as the wrong way to go about freezing for c/r.
You never explained why you had to do it this way. Why can't you inject
the parasite thread, move that thread out of the cgroup-to-be-frozen,
then freeze?
As best I can tell your reply last time only fleshed out the details
of *how* you would like it to work, not *why it needs to* work that way:
http://lkml.org/lkml/2011/11/30/27
Cheers,
-Matt Helsley
next prev parent reply other threads:[~2012-05-24 18:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 10:25 Cyrill Gorcunov
2012-05-23 10:25 ` [rfc v2 1/7] procfs: Move /proc/pid/fd[info] handling code to fd.[ch] Cyrill Gorcunov
2012-05-23 10:25 ` [rfc v2 2/7] procfs: Convert /proc/pid/fdinfo/ handling routines to seq-file Cyrill Gorcunov
2012-05-23 10:25 ` [rfc v2 3/7] procfs: Add ability to plugin auxiliary fdinfo providers Cyrill Gorcunov
2012-05-23 10:25 ` [rfc v2 4/7] fs, eventfd: Add procfs fdinfo helper Cyrill Gorcunov
2012-05-23 10:25 ` [rfc v2 5/7] fs, epoll: " Cyrill Gorcunov
2012-05-23 10:25 ` [rfc v2 6/7] fs, exportfs: Add export_encode_inode_fh helper Cyrill Gorcunov
2012-05-23 10:25 ` [rfc v2 7/7] fs, notify: Add procfs fdinfo helper Cyrill Gorcunov
2012-05-24 18:01 ` Matt Helsley [this message]
2012-05-24 18:23 ` [rfc v2 0/7] procfs fdinfo extension v2 Cyrill Gorcunov
2012-05-24 18:41 ` Cyrill Gorcunov
2012-05-24 19:48 ` Pavel Emelyanov
2012-05-24 20:27 ` Cyrill Gorcunov
2012-05-24 20:32 ` Matt Helsley
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=20120524180121.GK798@count0.beaverton.ibm.com \
--to=matthltc@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=gorcunov@openvz.org \
--cc=jbottomley@parallels.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skinsbursky@openvz.org \
--cc=tj@kernel.org \
--cc=xemul@parallels.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®