[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 11 Nov 2009 08:19:05 -0800
From: Arjan van de Ven <arjan@...radead.org>
To: Jeff Garzik <jeff@...zik.org>
Cc: Wu Fengguang <fengguang.wu@...el.com>,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
Christoph Hellwig <hch@...radead.org>,
Al Viro <viro@...IV.linux.org.uk>, mingo@...e.hu,
Frederic Weisbecker <fweisbec@...il.com>,
auke-jan.h.kok@...el.com
Subject: Re: [PATCH] vfs: Add a trace point in the mark_inode_dirty function
On Wed, 11 Nov 2009 02:42:39 -0500
Jeff Garzik <jeff@...zik.org> wrote:
> On 11/11/2009 01:34 AM, Arjan van de Ven wrote:
> > Wu Fengguang<fengguang.wu@...el.com> wrote:
> >> Maybe this is enough for POWERTOP, however for general use, the
> >> dirty type(data/metadata) and inode number may be valuable to some
> >> users?
> >
> > what can a user do with an inode number????
>
> Inode numbers have always been visible to userspace... IIRC, tar(1)
> uses the st_ino member of struct stat to detect hard links in certain
> cases. ls(1) displays inode numbers with -i, find(1) looks for them
> with -inum, ...
ok let me rephrase that. What would a user DO with this inode number
information, given that the filename is already passed on;
what additional useful, not-infinitely-hard-to-get piece of information
does this give the user that he can use to do <something> that he cannot
do with the current information ? E.g. what is that <something> ?
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists