doing a callback from the kernel to userspace
Quoted 4 lines
PS: Yes, I really do need this as signals form the kernel to userspace
add to much latency (10 to 20 usecs) and I want to avoid waiting in a system call.
The latency you talk about is the time required to schedule - there is nothing you driver can do to reduce that - syscall, signal or your own code must wait until schedule() decides to run your process.
I'd try to
a) switch your process to realtime priority, mlockall your app.
b) use the low-latency patches. They were regularly discussed on linux-kernel, search through the archives.
c) give up and implement everything in kernel.
d) switch to rtlinux.
Are you sure you need 10 to 20 usec? Then a hard realtime with everything in kernel is your only option, i.e. rtlinux.
--
Manfred
Quoted 8 lines · Manfred Spraul
The latency you talk about is the time required to schedule - there is nothing you driver can do to reduce that - syscall, signal or your own code must wait until
schedule()decides to run your process.I'd try to
a) switch your process to realtime priority, mlockall your app.
b) use the low-latency patches. They were regularly discussed on linux-kernel, search through the archives.
i'll definitely hav a look at these patches, thanks
Quoted 3 lines
Are you sure you need 10 to 20 usec? Then a hard realtime with everything in kernel is your only option, i.e. rtlinux.
Yes I'm sure and no, I don't think rtlinux is necessary, see my post answering Richard.
thanks again, maybe the ll-patches and some priority shifting is all I need _sh_