linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@openvz.org>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Pavel Emelyanov <xemul@parallels.com>,
	James Bottomley <jbottomley@parallels.com>,
	linux-fsdevel@vger.kernel.org
Subject: [rfc 0/4] procfs fdinfo extension
Date: Thu, 17 May 2012 20:07:38 +0400	[thread overview]
Message-ID: <20120517160738.116113099@openvz.org> (raw)

Hi guys,

when we do restore files such as eventfd/eventpoll we need to pass
appropriate parameters to system calls. Unfortunately there is no
easy way to retrieve this information from the kernel. So to make
possible to obtain this kind of information the proc/pid/fdinfo/fd
handling code has been modified to print "extra" snippets depending
on file type.

The base idea is to make fdinfo being seq-files and plug-in helpers.
For example eventpoll files together with basic pos/flags now print
out target file descriptor number, events and data associated with
an event:

 | pos:	0
 | flags:	02
 | tfd:        5 events:       1d data: ffffffffffffffff

This series is early draft not for inclusion yet but just to
gather people opinions on idea in general and implementation
details. I tried to make the change as small as I can.

I'm working on fsnotify part at moment but since it's not
yet complete decided to not include this patch, it'll appear
later.

(I've been said that idea of extending fdinfo to provide
 additional data snippets was approved on LSF this year.
 Am I right, Pavel?)

Any comments and complains are highly appreciated!

	Cyrill

             reply	other threads:[~2012-05-17 16:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17 16:07 Cyrill Gorcunov [this message]
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
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=20120517160738.116113099@openvz.org \
    --to=gorcunov@openvz.org \
    --cc=akpm@linux-foundation.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).