Hello, This week I worked on finding and fixing few pending issues, and worked on IN_MOVED_TO/IN_MOVED_FROM flags. I'm currertly working on binding these two together using cookie parament in inotify_event which I'm hoping should be completed by today or tomorrow.
Vishesh On Mon, Jul 16, 2012 at 08:32:00AM +0530, Vishesh Yadav wrote: > Date: Mon, 16 Jul 2012 08:32:00 +0530 > From: Vishesh Yadav <vishes...@gmail.com> > To: kernel@crater.dragonflybsd.org > Subject: Re: [GSoC] inotify and fs indexing service status > > Hello, > > This week I completed work on IN_CREATE and did some testing on inotify > and found few bugs. IN_CREATE created some new bugs too on which I'm > currently working on. > > Vishesh > > On 07/08/2012 09:41 PM, Vishesh Yadav wrote: > > Hello, > > > > This week I worked on NOTE_CREATE and IN_MOVED_* flags. These flags > > required some workaround as their behavior required a little more > > information than what is offered by kevent. There were few more problems > > with this including the merging of events in kqueue for which I'm trying to > > find a viable solution. > > > > Vishesh > > > > On Tue, Jul 3, 2012 at 12:10 PM, Vishesh Yadav <vishes...@gmail.com> wrote: > > > >> Hello, > >> > >> I wasn't able to put much work on code last week. Did some work on man > >> pages. > >> > >> Vishesh > >> > >> > >> On Tue, Jun 26, 2012 at 10:13 AM, Vishesh Yadav <vishes...@gmail.com>wrote: > >> > >>> Hello, > >>> > >>> In fifth week I implement idr - integer management library using code of > >>> file descriptor allocators in kern_descrip.c. Worked to use the new > >>> library > >>> to be used with filedesc, however something or other didn't work out. Will > >>> be trying that again after looking at code more properly. Rest tested > >>> existing work done till now which seems to work quite fine. There are > >>> mainly two events left to handle IN_MOVED_TO and IN_MOVED_FROM, which I'm > >>> being able to detect however have to synchronise them both using cookie > >>> argument. > >>> > >>> Vishesh > >>> > >>> > >>> On Mon, Jun 18, 2012 at 2:54 AM, Vishesh Yadav <vishes...@gmail.com>wrote: > >>> > >>>> Hello, > >>>> > >>>> This week's status - > >>>> > >>>> * Added following notes for EVFILT_VNODE - NOTE_OPEN, NOTE_ACCESS, > >>>> NOTE_CLOSE_WRITE, NOTE_CLOSE_NOWRITE, NOTE_CREATE. They work with Hammer > >>>> and UFS. > >>>> > >>>> * Implemented inotify_read() and have the most important masks working. > >>>> Hence now we have a working inotify system. > >>>> > >>>> Vishesh > >>>> > >>>> On 06/10/2012 11:42 PM, Vishesh Yadav wrote: > >>>>> Hello, > >>>>> > >>>>> 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 > >>>>> descriptors. > >>>>> > >>>>> Regards, > >>>>> Vishesh > >>>>> > >>>>> 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 <vishes...@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/ > >>>>>>> > >>>>>> > >>>>> > >>>>> > >>>> > >>>> > >>>> > >>> > >> > > > > -- -Vishesh
