Hi John.
On Sun, Nov 23, 2008 at 09:08:05PM -0800, John McCutchan ([EMAIL PROTECTED])
wrote:
> At this point I don't really want to see changes made to inotify. But,
> for arguments sake, why not something like inotify_init1 that takes a
> flag EXTENDED_EVENT which causes a larger event structure to be used.
> Something like,
>
> struct inotify_event_extended
> {
> s32 wd;
> u32 mask;
> u32 cookie;
> u32 data[4];
> char path[0];
> }
>
> The data array could be used to store arbitrary extra information,
> specified by flags.
What will happen when above array is not enough to store needed info?
Although I do not see any reason to send start/offset for the IO itself,
but if it will be decided to do so, above array already is not large
enough. I think I will cook up preliminary patch to add nested
attributes into event structure like I described previously in the
thread to get people involved with working example.
--
Evgeniy Polyakov
--
To unsubscribe from this list: send the line "unsubscribe linux-api" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
