[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [rtl] open/read/write in kernel space
- To: rtl@rtlinux.org
- Subject: Re: [rtl] open/read/write in kernel space
- From: Lothar Krause <loti@gmx.at>
- Date: Thu, 8 Mar 2001 01:49:26 +0100
- In-Reply-To: <200103071546.f27Fk1K18992@hq.fsmlabs.com>
- References: <200103071546.f27Fk1K18992@hq.fsmlabs.com>
- Reply-To: loti@gmx.at
Hi Erwin,
Gee okay, the sys_read() and sys_write() calls are rather short functions.
So I could both workaround changing ksyms.c and integrate the neccessary
segment descriptors manipulations. Is this playing around like complicated or
so? If this more than a 4 liner?
> I am currently working on a POSIX like aio module for RTAI. The
> module uses a number of kernel threads (basicly non realtime user
> programms
> running in kernel space) to do the IO via the sys_* functions.
> The communication between realtime and non realtime is based on LXRT
> (and with that not available for RT-linux but only for RTAI).
Otherwise I just rechecked the rtf_create() man page and didn't noticed the
O_NONBLOCK implied warning and nothing about buffer overflows. It this novel
in v3? That means basically I can just cat my data to a real time fifo and
read it without synchronization problems?
Throw them to the lions.
lo