From: Cyrill Gorcunov <gorcunov@openvz.org>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: 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: [rfc v2 0/7] procfs fdinfo extension v2
Date: Wed, 23 May 2012 14:25:41 +0400 [thread overview]
Message-ID: <20120523102541.382837149@openvz.org> (raw)
Hi guys,
here is an updated version of "get more detailed fdinfo" on
eventfd/epoll/fsnotify files. The main change from previous
version is that now almost everything is under CONFIG_CHECKPOINT_RESTORE
config symbol (except of conversion of fdinfo proc handling routines
to seq files which I think increase readability for mainline as well).
I've tried hard to minimaze impact on source code.
The comments and espec. complains are highly appreciated (even proposal
of some different design is welcome).
Andrew, as to questions what else needed for c/r in mainline -- that's
what I counted (at least at moment)
- fdinfo to restore eventfd/epoll/fsnotify (this series)
- restore of file-owner UIDs (there were a series from
Eric for mapping kernel-uids to user-uids, so I'm waiting
for their final merge before I adopt my patch and send it out
(maybe I've missed something and the whole Eric's series already
in linux-next, need to check)
- IPC c/r (there were a series from Stas not sure what status
of them at moment, as far as I remember they should be rewored)
- 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)
that's all I know.
Cyrill
next reply other threads:[~2012-05-23 10:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 10:25 Cyrill Gorcunov [this message]
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 ` [rfc v2 0/7] procfs fdinfo extension v2 Matt Helsley
2012-05-24 18:23 ` 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=20120523102541.382837149@openvz.org \
--to=gorcunov@openvz.org \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--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;
as well as URLs for NNTP newsgroup(s).