From: Gilad Ben-Yossef <gilad@benyossef.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: SA <bullet.train@ntlworld.com>, linux-kernel@vger.kernel.org
Subject: Re: device driver / char module interrupt vector -> user space code
Date: 09 Aug 2002 15:46:07 +0300 [thread overview]
Message-ID: <1028897167.27103.39.camel@sake> (raw)
In-Reply-To: <1028889240.30103.189.camel@irongate.swansea.linux.org.uk>
On Fri, 2002-08-09 at 13:34, Alan Cox wrote:
> On Fri, 2002-08-09 at 09:49, SA wrote:
> > I am writing a char module for a PCI stage controller and want to add the
> > following functionality;
> >
> > The device will generate an interrupt (or software trigger) and I want this to
> > run a bit of user code with relatively latency. (<1ms). I am unclear how to
> > do this while still separating the user from the kernel code and maintaining
> > security - would this usually be handled by issuing a signal to the user space
> > process? if so how and what latency can I expect?
>
> You could deliver a signal, or if appropriate you can have a system call
> that blocks until the IRQ. To get good reliable latency, mlockall() the
> process you need to be real time, and set it to a real time scheduling
> priority.
To get <1ms latencies I suspect you will also need the preemtive kernel
and lock-break patches (http://www.tech9.net/rml/linux/) and if you're
running on an x86, changing the HZ value in linux/asm/param.h from 100
to 1000 will also be a good idea IMHO.
Of course, this requires re-compiling and replacing the kernel which may
or may not be apropriate. AFAIK both the patches and the HZ value change
are already in the 2.5.x development kernels already, but not everyone
are running *that* version quite yet... :-D
Gilad.
--
Gilad Ben-Yossef <gilad@benyossef.com>
Code mangler, senior coffee drinker and VP SIGSEGV
Qlusters ltd.
"You got an EMP device in the server room? That is so cool."
-- from a hackers-il thread on paranoia
prev parent reply other threads:[~2002-08-09 12:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 8:49 device driver / char module interrupt vector -> user space code SA
2002-08-09 10:34 ` Alan Cox
2002-08-09 9:35 ` Jan Hudec
2002-08-09 12:46 ` Gilad Ben-Yossef [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1028897167.27103.39.camel@sake \
--to=gilad@benyossef.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bullet.train@ntlworld.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox