DragonFly kernel List (threaded) for 2012-08
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]
Re: [GSoC] inotify and fs indexing service status
--f46d0401678b71749d04c713ab61
Content-Type: text/plain; charset=ISO-8859-1
Hello,
Not much code this week. Mainly improved few parts (copyout, read and watch
delete parts) and fixed couple of issues related to events. I'm currently
trying to compile and test gamin and working on man pages and documentation.
Vishesh
On Mon, Aug 6, 2012 at 12:05 AM, Vishesh Yadav <vishesh3y@gmail.com> wrote:
> Hello,
>
> inotify now supports all the flags and works. There is an issue with
> ordering of IN_MOVED_TO and IN_MOVED_FROM events which isn't similar to
> Linux behaviour. I will be spending this week testing and improving
> existing work.
>
> Vishesh
>
> On 07/30/2012 09:01 PM, Vishesh Yadav wrote:
> > Hello,
> >
> > This week I worked on idr library and it now seems ready to work and is
> > Linux compatible (except idr_pre_get() which takes one less argument than
> > and the return codes.).
> >
> > Vishesh
> >
> > On Mon, Jul 23, 2012 at 2:50 PM, Vishesh Yadav <vishesh3y@gmail.com>
> wrote:
> >
> >> 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 <vishesh3y@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 <vishesh3y@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 <vishesh3y@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 <vishesh3y@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 <
> >> 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/
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >>
> >> --
> >> -Vishesh
> >>
> >
>
>
--f46d0401678b71749d04c713ab61
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Hello,<br><br>Not much code this week. Mainly improved few parts (copyout, =
read and watch delete parts) and fixed couple of issues related to events. =
I'm currently trying to compile and test gamin and working on man pages=
and documentation.<br>
<br>Vishesh<br><br><div class=3D"gmail_quote">On Mon, Aug 6, 2012 at 12:05 =
AM, Vishesh Yadav <span dir=3D"ltr"><<a href=3D"mailto:vishesh3y@gmail.c=
om" target=3D"_blank">vishesh3y@gmail.com</a>></span> wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">
Hello,<br>
<br>
inotify now supports all the flags and works. There is an issue with<br>
ordering of IN_MOVED_TO and IN_MOVED_FROM events which isn't similar to=
<br>
Linux behaviour. I will be spending this week testing and improving<br>
existing work.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Vishesh<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
On 07/30/2012 09:01 PM, Vishesh Yadav wrote:<br>
> Hello,<br>
><br>
> This week I worked on idr library and it now seems ready to work and i=
s<br>
> Linux compatible (except idr_pre_get() which takes one less argument t=
han<br>
> and the return codes.).<br>
><br>
> Vishesh<br>
><br>
> On Mon, Jul 23, 2012 at 2:50 PM, Vishesh Yadav <<a href=3D"mailto:v=
ishesh3y@gmail.com">vishesh3y@gmail.com</a>> wrote:<br>
><br>
>> Hello,<br>
>><br>
>> This week I worked on finding and fixing few pending issues, and w=
orked<br>
>> on IN_MOVED_TO/IN_MOVED_FROM flags. I'm currertly working on b=
inding<br>
>> these two together using cookie parament in inotify_event which I&=
#39;m<br>
>> hoping should be completed by today or tomorrow.<br>
>><br>
>> Vishesh<br>
>><br>
>> On Mon, Jul 16, 2012 at 08:32:00AM +0530, Vishesh Yadav wrote:<br>
>>> Date: Mon, 16 Jul 2012 08:32:00 +0530<br>
>>> From: Vishesh Yadav <<a href=3D"mailto:vishesh3y@gmail.com"=
>vishesh3y@gmail.com</a>><br>
>>> To: <a href=3D"mailto:kernel@crater.dragonflybsd.org";>kernel@c=
rater.dragonflybsd.org</a><br>
>>> Subject: Re: [GSoC] inotify and fs indexing service status<br>
>>><br>
>>> Hello,<br>
>>><br>
>>> This week I completed work on IN_CREATE and did some testing o=
n inotify<br>
>>> and found few bugs. IN_CREATE created some new bugs too on whi=
ch I'm<br>
>>> currently working on.<br>
>>><br>
>>> Vishesh<br>
>>><br>
>>> On 07/08/2012 09:41 PM, Vishesh Yadav wrote:<br>
>>>> Hello,<br>
>>>><br>
>>>> This week I worked on NOTE_CREATE and IN_MOVED_* flags. Th=
ese flags<br>
>>>> required some workaround as their behavior required a litt=
le more<br>
>>>> information than what is offered by kevent. There were few=
more<br>
>> problems<br>
>>>> with this including the merging of events in kqueue for wh=
ich I'm<br>
>> trying to<br>
>>>> find a viable solution.<br>
>>>><br>
>>>> Vishesh<br>
>>>><br>
>>>> On Tue, Jul 3, 2012 at 12:10 PM, Vishesh Yadav <<a href=
=3D"mailto:vishesh3y@gmail.com";>vishesh3y@gmail.com</a>><br>
>> wrote:<br>
>>>><br>
>>>>> Hello,<br>
>>>>><br>
>>>>> I wasn't able to put much work on code last week. =
Did some work on man<br>
>>>>> pages.<br>
>>>>><br>
>>>>> Vishesh<br>
>>>>><br>
>>>>><br>
>>>>> On Tue, Jun 26, 2012 at 10:13 AM, Vishesh Yadav <<a=
href=3D"mailto:vishesh3y@gmail.com";>vishesh3y@gmail.com</a><br>
>>> wrote:<br>
>>>>><br>
>>>>>> Hello,<br>
>>>>>><br>
>>>>>> In fifth week I implement idr - integer management=
library using<br>
>> code of<br>
>>>>>> file descriptor allocators in kern_descrip.c. Work=
ed to use the new<br>
>> library<br>
>>>>>> to be used with filedesc, however something or oth=
er didn't work<br>
>> out. Will<br>
>>>>>> be trying that again after looking at code more pr=
operly. Rest tested<br>
>>>>>> existing work done till now which seems to work qu=
ite fine. There are<br>
>>>>>> mainly two events left to handle IN_MOVED_TO and I=
N_MOVED_FROM,<br>
>> which I'm<br>
>>>>>> being able to detect however have to synchronise t=
hem both using<br>
>> cookie<br>
>>>>>> argument.<br>
>>>>>><br>
>>>>>> Vishesh<br>
>>>>>><br>
>>>>>><br>
>>>>>> On Mon, Jun 18, 2012 at 2:54 AM, Vishesh Yadav <=
;<a href=3D"mailto:vishesh3y@gmail.com";>vishesh3y@gmail.com</a><br>
>>> wrote:<br>
>>>>>><br>
>>>>>>> Hello,<br>
>>>>>>><br>
>>>>>>> This week's status -<br>
>>>>>>><br>
>>>>>>> * Added following notes for EVFILT_VNODE - NOT=
E_OPEN, NOTE_ACCESS,<br>
>>>>>>> NOTE_CLOSE_WRITE, NOTE_CLOSE_NOWRITE, NOTE_CRE=
ATE. They work with<br>
>> Hammer<br>
>>>>>>> and UFS.<br>
>>>>>>><br>
>>>>>>> * Implemented inotify_read() and have the most=
important masks<br>
>> working.<br>
>>>>>>> Hence now we have a working inotify system.<br=
>
>>>>>>><br>
>>>>>>> Vishesh<br>
>>>>>>><br>
>>>>>>> On 06/10/2012 11:42 PM, Vishesh Yadav wrote:<b=
r>
>>>>>>>> Hello,<br>
>>>>>>>><br>
>>>>>>>> Not much new code this week. Improved and =
tested existing code,<br>
>> exposed<br>
>>>>>>>> watch/instance limits through sysctl and m=
ade the system respect<br>
>> the<br>
>>>>>>> limits.<br>
>>>>>>>><br>
>>>>>>>> Rest studied kernel kqueue interface and i=
ts usage to be used in<br>
>>>>>>>> inotify_read. Planned to add few knotes li=
ke NOTE_ACCESS,<br>
>> NOTE_CLOSE<br>
>>>>>>> and<br>
>>>>>>>> linux like idr integer management that can=
be used in fdalloc and<br>
>> watch<br>
>>>>>>>> descriptors.<br>
>>>>>>>><br>
>>>>>>>> Regards,<br>
>>>>>>>> Vishesh<br>
>>>>>>>><br>
>>>>>>>> On 06/03/2012 10:14 PM, Vishesh Yadav wrot=
e:<br>
>>>>>>>>> Hello,<br>
>>>>>>>>><br>
>>>>>>>>> This week I finished watch management =
functions. Now watches can<br>
>> be<br>
>>>>>>> added,<br>
>>>>>>>>> removed from into the inotify_instance=
. Hence inotify_add_watch,<br>
>>>>>>>>> inotify_rm_watch are now almost comple=
te. Just have to check error<br>
>>>>>>> codes<br>
>>>>>>>>> that are being returned. I also implem=
ented fo_close for inotify<br>
>>>>>>> fileops<br>
>>>>>>>>> which cleans up the instance well now.=
<br>
>>>>>>>>><br>
>>>>>>>>> Regards,<br>
>>>>>>>>> Vishesh<br>
>>>>>>>>><br>
>>>>>>>>> On Sat, May 26, 2012 at 7:07 PM, Vishe=
sh Yadav <<br>
>> <a href=3D"mailto:vishesh3y@gmail.com";>vishesh3y@gmail.com</a>>=
<br>
>>>>>>> wrote:<br>
>>>>>>>>><br>
>>>>>>>>>> Hello everyone,<br>
>>>>>>>>>><br>
>>>>>>>>>> Current status for first week -<br=
>
>>>>>>>>>><br>
>>>>>>>>>> - Repository and wiki setup at Git=
hub[1]<br>
>>>>>>>>>> - Made the basic skeleton for inot=
ify interface - system calls,<br>
>>>>>>> helper<br>
>>>>>>>>>> functions, structures, headers and=
few basic stuff in there.<br>
>>>>>>>>>> - Currently working on management =
of watches (will be using<br>
>> separate<br>
>>>>>>>>>> file tables for watches). Once thi=
s is done, can write some<br>
>> working<br>
>>>>>>> code.<br>
>>>>>>>>>><br>
>>>>>>>>>> In community bonding period, I set=
up my working environment,<br>
>> browse<br>
>>>>>>> and<br>
>>>>>>>>>> understood relevant kernel codebas=
e and studied Linux early and<br>
>>>>>>> recent<br>
>>>>>>>>>> inotify implementation.<br>
>>>>>>>>>><br>
>>>>>>>>>> Now that exams are almost over, I =
hope I can catch up some pace<br>
>> now.<br>
>>>>>>>>>><br>
>>>>>>>>>> Regards,<br>
>>>>>>>>>> Vishesh<br>
>>>>>>>>>><br>
>>>>>>>>>> [1] <a href=3D"https://github.com/=
vishesh/DragonFlyBSD/" target=3D"_blank">https://github.com/vishesh/DragonF=
lyBSD/</a><br>
>>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>><br>
>>>>><br>
>>>><br>
>>><br>
>>><br>
>><br>
>> --<br>
>> =A0 =A0 =A0 =A0 -Vishesh<br>
>><br>
><br>
<br>
</div></div></blockquote></div><br>
--f46d0401678b71749d04c713ab61--
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]
