From: Stelian Pop <stelian.pop@fr.alcove.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCI driver in userspace
Date: Wed, 27 Feb 2002 09:26:42 +0100 [thread overview]
Message-ID: <20020227082642.GA19173@come.alcove-fr> (raw)
In-Reply-To: <D8E12241B029D411A3A300805FE6A2B9025761AB@montreal.eicon.com> <mailman.1014747181.29305.linux-kernel2news@redhat.com> <200202270052.g1R0qdK11879@devserv.devel.redhat.com>
In-Reply-To: <200202270052.g1R0qdK11879@devserv.devel.redhat.com>
On Tue, Feb 26, 2002 at 07:52:39PM -0500, Pete Zaitcev wrote:
[Interrupts in userspace...]
> >> Although I dont know if this is a good idea in the first place.
> >
> > I think it depends on the interrupt frequency, and other things.
> >
> This is why purely
> user level interrupts are IMPOSSIBLE (regardless of interrupt
> frequency).
[...]
> 2. Write a small driver that deactivates interrupts and queues
> interrupt events (with SIGIO and some other means).
This is what I meant too, and I was talking about the interrupt
frequency because if there are too many IT, continuous polling might
be more efficient than interrupt handling with the kernel driver +
userspace signal sending.
> Very many people are psychologically afraid of drivers
> (even though it's quite simple), and they wank those userspace
> approaches, until they hit some brick wall (interrupts being
> most common). By that time they invest so much into their code
> that they are loth to abandon broken userland drivers and
> start grappling about desperately for a way out.
It depends on the driver. If moving _all_ the driver in kernelspace
involves putting policy and other stuff into the kernel, then no.
Stelian.
--
Stelian Pop <stelian.pop@fr.alcove.com>
Alcove - http://www.alcove.com
next prev parent reply other threads:[~2002-02-27 8:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1014747181.29305.linux-kernel2news@redhat.com>
2002-02-26 17:42 ` Daniel Shane
2002-02-26 18:10 ` Stelian Pop
2002-02-27 0:52 ` Pete Zaitcev
2002-02-27 8:26 ` Stelian Pop [this message]
2002-02-27 0:59 ` Richard Gooch
2002-02-26 14:55 Daniel Shane
2002-02-26 15:07 ` Martin Dalecki
2002-02-26 15:12 ` Stelian Pop
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=20020227082642.GA19173@come.alcove-fr \
--to=stelian.pop@fr.alcove.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.com \
/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®