[GSOC] System V IPC in userspace week2 report (Larisa Grigore)

[grigore larisa <larisagrigore@xxxxxxxxx>]

--089e01183b60bc67a204e0647dd6
Content-Type: text/plain; charset=ISO-8859-1

Hello everyone,

This week I have implemented a driver with open, close, ioctl and kqfilter
functions. Only one process can be registered as a daemon and it will be
responsible for sysv ipc resources.

The daemon waits for data from the driver and from pipes, using poll call.
When it receives data from the driver, it means that a new client wants to
connect to it. The daemon will create unnamed pipes to communicate with the
client using the driver again.
For now on, the communication between the daemon and a registered client is
made using the created pipes.
Clients can register to the daemon through an ioctl call.

Thanks,
Larisa Grigore

--089e01183b60bc67a204e0647dd6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello everyone,<div><br></div><div style>This week I have =
implemented a driver with open, close, ioctl and kqfilter functions. Only o=
ne process can be registered as a daemon and it will be responsible for sys=
v ipc resources.</div>
<div style><br></div><div style>The daemon waits for data from the driver a=
nd from pipes, using poll call. When it receives data from the driver, it m=
eans that a new client wants to connect to it. The daemon will create unnam=
ed pipes to communicate with the client using the driver again.</div>
<div style>For now on, the communication between the daemon and a registere=
d client is made using the created pipes.</div><div style>Clients can regis=
ter to the daemon through an ioctl call.</div><div style><br></div><div sty=
le>
Thanks,</div><div style>Larisa Grigore</div></div>

--089e01183b60bc67a204e0647dd6--