Re: [take2] Inotify: nested attributes support.
flat view
From: Evgeniy Polyakov <hidden>
Date: 2008-11-26 08:29:48
Also in:
lkml
On Wed, Nov 26, 2008 at 12:15:38AM -0800, Andrew Morton (akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org) wrote:
OK, so we have a super-duper framework which will allow us to add pids (and other things) to inotify messages.
Yup :)
This still doesn't provide a reason for anyone to be interested in the code! Why do we want pids in inotify messages?
I actually cared only about myself :) I started the thread and implementation, because my application has to differentiate IO made by itself and any IO made by system (another users, crons, whatever else), inotify did not give me that info, so I extended it. As of others: PID/TID may be used by watching applications to reduce own load to not process own IO, things like beagle may show who actually made changes into the file.
And how does this work give that pids are (no longer) system-wide unique?
It gets pids from the caller's task_struct (via current), so its data is as unique as process calling getpid() or syscall(__NR_gettid). -- Evgeniy Polyakov -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html