DragonFly kernel List (threaded) for 2012-07
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]
Re: [GSoC] inotify and fs indexing service status
--f46d042f927a6d46b504c3e73104
Content-Type: text/plain; charset=ISO-8859-1
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/
>> >>>
>> >>
>> >
>> >
>>
>>
>>
>
--f46d042f927a6d46b504c3e73104
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Hello,<br><br>I wasn't able to put much work on code last week. Did som=
e work on man pages.<br><br>Vishesh<br><br><div class=3D"gmail_quote">On Tu=
e, Jun 26, 2012 at 10:13 AM, Vishesh Yadav <span dir=3D"ltr"><<a href=3D=
"mailto:vishesh3y@gmail.com"; target=3D"_blank">vishesh3y@gmail.com</a>><=
/span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hello,<br><br>In fifth week I implement idr =
- integer management library using code of file descriptor allocators in ke=
rn_descrip.c. Worked to use the new library to be used with filedesc, howev=
er 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 whic=
h seems to work quite fine. There are mainly two events left to handle IN_M=
OVED_TO and IN_MOVED_FROM, which I'm being able to detect however have =
to synchronise them both using cookie argument.<span class=3D"HOEnZb"><font=
color=3D"#888888"><br>
<br>Vishesh</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br><br><d=
iv class=3D"gmail_quote">On Mon, Jun 18, 2012 at 2:54 AM, Vishesh Yadav <sp=
an dir=3D"ltr"><<a href=3D"mailto:vishesh3y@gmail.com"; target=3D"_blank"=
>vishesh3y@gmail.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hello,<br>
<br>
This week's status -<br>
<br>
* Added following notes for EVFILT_VNODE - NOTE_OPEN, NOTE_ACCESS,<br>
NOTE_CLOSE_WRITE, NOTE_CLOSE_NOWRITE, NOTE_CREATE. They work with Hammer<br=
>
and UFS.<br>
<br>
* Implemented inotify_read() and have the most important masks working.<br>
Hence now we have a working inotify system.<br>
<span><font color=3D"#888888"><br>
Vishesh<br>
</font></span><div><div><br>
On 06/10/2012 11:42 PM, Vishesh Yadav wrote:<br>
> Hello,<br>
><br>
> Not much new code this week. Improved and tested existing code, expose=
d<br>
> watch/instance limits through sysctl and made the system respect the l=
imits.<br>
><br>
> Rest studied kernel kqueue interface and its usage to be used in<br>
> inotify_read. Planned to add few knotes like NOTE_ACCESS, NOTE_CLOSE a=
nd<br>
> linux like idr integer management that can be used in fdalloc and watc=
h<br>
> descriptors.<br>
><br>
> Regards,<br>
> Vishesh<br>
><br>
> On 06/03/2012 10:14 PM, Vishesh Yadav wrote:<br>
>> Hello,<br>
>><br>
>> This week I finished watch management functions. Now watches can b=
e added,<br>
>> removed from into the inotify_instance. Hence inotify_add_watch,<b=
r>
>> inotify_rm_watch are now almost complete. Just have to check error=
codes<br>
>> that are being returned. I also implemented fo_close for inotify f=
ileops<br>
>> which cleans up the instance well now.<br>
>><br>
>> Regards,<br>
>> Vishesh<br>
>><br>
>> On Sat, May 26, 2012 at 7:07 PM, Vishesh Yadav <<a href=3D"mail=
to:vishesh3y@gmail.com" target=3D"_blank">vishesh3y@gmail.com</a>> wrote=
:<br>
>><br>
>>> Hello everyone,<br>
>>><br>
>>> Current status for first week -<br>
>>><br>
>>> - Repository and wiki setup at Github[1]<br>
>>> - Made the basic skeleton for inotify interface - system calls=
, helper<br>
>>> functions, structures, headers and few basic stuff in there.<b=
r>
>>> - Currently working on management of watches (will be using se=
parate<br>
>>> file tables for watches). Once this is done, can write some wo=
rking code.<br>
>>><br>
>>> In community bonding period, I setup my working environment, b=
rowse and<br>
>>> understood relevant kernel codebase and studied Linux early an=
d recent<br>
>>> inotify implementation.<br>
>>><br>
>>> Now that exams are almost over, I hope I can catch up some pac=
e now.<br>
>>><br>
>>> Regards,<br>
>>> Vishesh<br>
>>><br>
>>> [1] <a href=3D"https://github.com/vishesh/DragonFlyBSD/"; targe=
t=3D"_blank">https://github.com/vishesh/DragonFlyBSD/</a><br>
>>><br>
>><br>
><br>
><br>
<br>
<br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>
--f46d042f927a6d46b504c3e73104--
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]
