From: Andrew Morton <akpm@linux-foundation.org>
To: Cyrill Gorcunov <gorcunov@openvz.org>
Cc: linux-kernel@vger.kernel.org,
Pavel Emelyanov <xemul@parallels.com>,
James Bottomley <jbottomley@parallels.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [rfc 0/4] procfs fdinfo extension
Date: Thu, 17 May 2012 12:05:41 -0700 [thread overview]
Message-ID: <20120517120541.f2dbdee9.akpm@linux-foundation.org> (raw)
In-Reply-To: <20120517160738.116113099@openvz.org>
On Thu, 17 May 2012 20:07:38 +0400
Cyrill Gorcunov <gorcunov@openvz.org> wrote:
> when we do restore files such as eventfd/eventpoll we need to pass
> appropriate parameters to system calls.
What does "such as" mean? Provide the whole list, please. I assume
we're going to have to add ~100 lines of stuff to each and every one?
Stuff which, according to this patchset, is needed even when
CONFIG_CHECKPOINT_RESTORE=n?
My reason for disliking our whole approach to integration of c/r is
that it exposes us to an ongoing trickle of nasty surprises. This
patchset is one such nasty surprise, and we don't even know how
extensive this particular surprise will be.
And how many more surprises are we going to get?
I'm quite apprehensive about this, largely because it has so many
unknowns. How much work would it be to prepare a full list of
everything that still needs to be done to fully implement c/r in Linux?
next prev parent reply other threads:[~2012-05-17 19:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 16:07 [rfc 0/4] procfs fdinfo extension Cyrill Gorcunov
2012-05-17 16:07 ` [rfc 1/4] procfs: Move /proc/pid/fd[info] handling code to fd.[ch] Cyrill Gorcunov
2012-05-17 16:07 ` [rfc 2/4] procfs: Convert /proc/pid/fdinfo/fd handling routines into seq-file with fdinfo helpers Cyrill Gorcunov
2012-05-17 16:32 ` Pavel Emelyanov
2012-05-17 17:38 ` Cyrill Gorcunov
2012-05-17 21:49 ` Cyrill Gorcunov
2012-05-17 16:07 ` [rfc 3/4] fs, eventfd: Add procfs fdinfo helper Cyrill Gorcunov
2012-05-17 16:34 ` Pavel Emelyanov
2012-05-17 17:43 ` Cyrill Gorcunov
2012-05-17 16:07 ` [rfc 4/4] fs, epoll: " Cyrill Gorcunov
2012-05-17 16:29 ` [rfc 0/4] procfs fdinfo extension Pavel Emelyanov
2012-05-17 19:05 ` Andrew Morton [this message]
2012-05-17 19:28 ` Cyrill Gorcunov
2012-05-18 11:53 ` Pavel Emelyanov
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=20120517120541.f2dbdee9.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gorcunov@openvz.org \
--cc=jbottomley@parallels.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.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).