LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>, linux-kernel@vger.kernel.org
Subject: Re: [patch] add file position info to proc
Date: Mon, 26 Mar 2007 10:05:02 +1000	[thread overview]
Message-ID: <17927.3630.414133.365527@notabene.brown> (raw)
In-Reply-To: message from Andrew Morton on Sunday March 25

On Sunday March 25, akpm@linux-foundation.org wrote:
> On Sat, 24 Mar 2007 23:04:09 +0100 Miklos Szeredi <miklos@szeredi.hu> wrote:
> 
> > This patch adds support for finding out the current file position,
> > open flags and possibly other info in the future.
> > 
> > These new entries are added:
> > 
> >   /proc/PID/fdinfo/FD
> >   /proc/PID/task/TID/fdinfo/FD
> > 
> > For each fd the information is provided in the following format:
> > 
> > pos:	1234
> > flags:	0100002
> 
> I've seen the idea mentioned once or twice, but not with any great
> enthusiasm.  Why does Linux want this feature?

Same reason we want ltrace and lsof.  To be able to look inside a
process and see what it is doing.
e.g. how far has that program got through reading that enormous file?
is it really making progress, or is it going much more slowly than I
would expect and so should I look more deeply.

I'm in favour.

NeilBrown

  reply	other threads:[~2007-03-26  0:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-24 22:04 Miklos Szeredi
2007-03-25 23:45 ` Andrew Morton
2007-03-26  0:05   ` Neil Brown [this message]
2007-03-26  9:41   ` Folkert van Heusden
2007-03-27 21:55   ` Dave Hansen
2007-03-27  0:45 ` Andrew Morton
2007-03-27  7:08   ` Miklos Szeredi
2007-03-27  7:35     ` Andrew Morton
2007-03-27 21:24 ` Pavel Machek
2007-03-27 21:33   ` Jörn Engel
2007-03-27 21:36   ` Andrew Morton
2007-03-27 21:43     ` Miklos Szeredi
2007-03-27 22:33       ` Pavel Machek
2007-03-27 23:05         ` Miklos Szeredi

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=17927.3630.414133.365527@notabene.brown \
    --to=neilb@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --subject='Re: [patch] add file position info to proc' \
    /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

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).