DragonFly BSD
DragonFly kernel List (threaded) for 2012-06
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: [GSoC] inotify and fs indexing service status

From: Vishesh Yadav <vishesh3y@xxxxxxxxx>
Date: Sun, 10 Jun 2012 23:42:30 +0530


Not much new code this week. Improved and tested existing code, exposed
watch/instance limits through sysctl and made the system respect the limits.

Rest studied kernel kqueue interface and its usage to be used in
inotify_read. Planned to add few knotes like NOTE_ACCESS, NOTE_CLOSE and
linux like idr integer management that can be used in fdalloc and watch


On 06/03/2012 10:14 PM, Vishesh Yadav wrote:
> Hello,
> This week I finished watch management functions. Now watches can be added,
> removed from into the inotify_instance. Hence inotify_add_watch,
> inotify_rm_watch are now almost complete. Just have to check error codes
> that are being returned. I also implemented fo_close for inotify fileops
> which cleans up the instance well now.
> Regards,
> Vishesh
> On Sat, May 26, 2012 at 7:07 PM, Vishesh Yadav <vishesh3y@gmail.com> wrote:
>> Hello everyone,
>> Current status for first week -
>> - Repository and wiki setup at Github[1]
>> - Made the basic skeleton for inotify interface - system calls, helper
>> functions, structures, headers and few basic stuff in there.
>> - Currently working on management of watches (will be using separate
>> file tables for watches). Once this is done, can write some working code.
>> In community bonding period, I setup my working environment, browse and
>> understood relevant kernel codebase and studied Linux early and recent
>> inotify implementation.
>> Now that exams are almost over, I hope I can catch up some pace now.
>> Regards,
>> Vishesh
>> [1] https://github.com/vishesh/DragonFlyBSD/

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