Re: Design of fsnotify for FUSE, nfs and cifs: when/how to send a watch.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I guess with performance you mean the performance of reporting events.
I understand it
can be a performance issue when there are a lot of events.

I haven't tested that yet. The events are received by the userspace
daemon, and if they are not initiated by this daemon self,
they are send to the VFS with just inodenumber, mask and eventually
the name of the entry. There a lookup is done of the inode using
ilookup5, and reported to fsnotify using the common function fsnotify,
defined in fsnotify.c, 190.

Well I know I have to test this by creating and deleting a lot of
files in the watched directory. I will report later.

Stef
--
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux