From: "Hans-Jürgen Koch" <hjk@linutronix.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Userspace I/O driver core
Date: Thu, 14 Dec 2006 11:25:14 +0100 [thread overview]
Message-ID: <200612141125.14777.hjk@linutronix.de> (raw)
In-Reply-To: <45811D0F.2070705@argo.co.il>
Am Donnerstag, 14. Dezember 2006 10:44 schrieb Avi Kivity:
>
> I understand one still has to write a kernel driver to shut up the irq.
> How about writing a small bytecode interpreter to make event than
> unnecessary?
>
> The userspace driver would register a couple of bytecode programs:
> is_interrupt_pending() and disable_interrupt(), which the uio framework
> would call when the interrupt fires.
>
> The bytecode could reuse net/core/filter.c, with the packet replaced by
> the mmio or ioregion, or use something new.
>
I think this would be overkill. The kernel module you have to write
is _really_ very simple. And it has to be written only once, so even
a manufacturer who employs no experienced kernel developers can
easily outsource that task.
Hans
next prev parent reply other threads:[~2006-12-14 10:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 1:06 Greg KH
2006-12-14 5:48 ` Ben Nizette
2006-12-14 9:44 ` Avi Kivity
2006-12-14 10:19 ` Arjan van de Ven
2006-12-14 10:46 ` Avi Kivity
2006-12-14 10:54 ` Arjan van de Ven
2006-12-14 10:56 ` Avi Kivity
2006-12-14 17:54 ` Greg KH
2006-12-16 14:48 ` Dr. David Alan Gilbert
2006-12-14 10:25 ` Hans-Jürgen Koch [this message]
2006-12-14 10:48 ` Avi Kivity
2006-12-14 12:39 ` Jan Engelhardt
2006-12-14 13:38 ` Avi Kivity
2006-12-14 17:48 ` Jan Engelhardt
2006-12-14 18:00 ` Greg KH
2006-12-14 10:52 ` Alan
2006-12-14 11:22 ` Thomas Gleixner
2006-12-14 11:39 ` Alan
2006-12-14 11:37 ` Hans-Jürgen Koch
2006-12-14 12:45 ` Alan
2006-12-14 12:37 ` Jan Engelhardt
2006-12-14 16:10 ` linux-os (Dick Johnson)
2006-12-14 21:55 ` Ben Nizette
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=200612141125.14777.hjk@linutronix.de \
--to=hjk@linutronix.de \
--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
all inboxes | Powered by JetHome®