mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@openvz.org>
To: linux-kernel@vger.kernel.org
Cc: shawn@churchofgit.com, tglx@linutronix.de,
	akpm@linux-foundation.org, avagin@openvz.org,
	xemul@parallels.com, gorcunov@openvz.org, vdavydov@parallels.com
Subject: [patch 2/3] docs: procfs -- Document timerfd output
Date: Tue, 29 Apr 2014 01:25:19 +0400	[thread overview]
Message-ID: <20140428213301.406805138@openvz.org> (raw)
In-Reply-To: <20140428212517.200264067@openvz.org>

[-- Attachment #1: timerfd-doc-fdinfo --]
[-- Type: text/plain, Size: 1617 bytes --]

CC: Shawn Landden <shawn@churchofgit.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: Andrey Vagin <avagin@openvz.org>
CC: Pavel Emelyanov <xemul@parallels.com>
CC: Vladimir Davydov <vdavydov@parallels.com>
Signed-off-by: Cyrill Gorcunov <gorcunov@openvz.org>
---
 Documentation/filesystems/proc.txt |   19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

Index: linux-2.6.git/Documentation/filesystems/proc.txt
===================================================================
--- linux-2.6.git.orig/Documentation/filesystems/proc.txt
+++ linux-2.6.git/Documentation/filesystems/proc.txt
@@ -1741,6 +1741,25 @@ pair provide additional information part
 	While the first three lines are mandatory and always printed, the rest is
 	optional and may be omitted if no marks created yet.
 
+	Timerfd files
+	~~~~~~~~~~~~~
+
+	pos:	0
+	flags:	02
+	mnt_id:	9
+	clockid: 0
+	ticks: 0
+	settime flags: 01
+	it_value: (0, 49406829)
+	it_interval: (1, 0)
+
+	where 'clockid' is the clock type and 'ticks' is the number of the timer expirations
+	that have occurred [see timerfd_create(2) for details]. 'settime flags' are
+	flags in octal form used to setup the timer [see timerfd_settime(2) for
+	details]. 'it_value' is remaining time until the timer exiration.
+	'it_interval' is the interval for the timer. Note the timer might be set
+	up with TFD_TIMER_ABSTIME option which will be shown in 'settime flags',
+	but 'it_value' still exhibit timer's remaining time.
 
 ------------------------------------------------------------------------------
 Configuring procfs


  parent reply	other threads:[~2014-04-28 21:33 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28 21:25 [patch 0/3] timerfd -- implement missing parts to checkpoint and restore timerfd state, v3 Cyrill Gorcunov
2014-04-28 21:25 ` [patch 1/3] timerfd: Implement show_fdinfo method Cyrill Gorcunov
2014-05-21 21:41   ` Thomas Gleixner
2014-05-21 21:54     ` Cyrill Gorcunov
2014-04-28 21:25 ` Cyrill Gorcunov [this message]
2014-04-28 21:25 ` [patch 3/3] timerfd: Implement write method Cyrill Gorcunov
2014-05-21 21:43   ` Thomas Gleixner
2014-05-21 21:57     ` Cyrill Gorcunov
2014-05-21 22:12       ` Thomas Gleixner
2014-05-21 22:35         ` Cyrill Gorcunov
2014-05-21 23:30           ` Thomas Gleixner
2014-05-22  5:31             ` Cyrill Gorcunov
2014-05-22  6:32           ` Michael Kerrisk
2014-05-22  7:03             ` Cyrill Gorcunov
     [not found]   ` <alpine.DEB.2.02.1405220643170.9695@ionos.tec.linutronix.de>
2014-05-21 21:58     ` Thomas Gleixner
2014-06-10 16:35       ` Cyrill Gorcunov
2014-06-10 20:03         ` Michael Kerrisk (man-pages)
2014-06-10 20:05           ` Andy Lutomirski
2014-06-10 20:22             ` Cyrill Gorcunov
2014-06-11  7:27         ` Andrew Vagin
2014-06-11  7:51           ` Cyrill Gorcunov
2014-06-11  9:09             ` Andrew Vagin
2014-06-11  9:52               ` Cyrill Gorcunov
2014-06-11 12:43                 ` Cyrill Gorcunov
2014-05-21 10:03 ` [patch 0/3] timerfd -- implement missing parts to checkpoint and restore timerfd state, v3 Cyrill Gorcunov
  -- strict thread matches above, loose matches on Subject: below --
2014-04-07 17:47 [patch 0/3] timerfd -- implement missing parts to checkpoint and restore timerfd state, v2 Cyrill Gorcunov
2014-04-07 17:47 ` [patch 2/3] docs: procfs -- Document timerfd output Cyrill Gorcunov

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=20140428213301.406805138@openvz.org \
    --to=gorcunov@openvz.org \
    --cc=akpm@linux-foundation.org \
    --cc=avagin@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shawn@churchofgit.com \
    --cc=tglx@linutronix.de \
    --cc=vdavydov@parallels.com \
    --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

Powered by JetHome