From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: viability of supporting interrupts in user space driver?
Date: Fri, 20 Nov 2015 04:39:45 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.20.1511200437130.442@localhost> (raw)
In-Reply-To: <871tblhxlw.fsf@fatcat.parallelwireless>
On Fri, 20 Nov 2015, Anupam Kapoor wrote:
>
> >>>>> [2015-11-20T13:08:46+0530]: "Robert P. J. Day" (robert-pj-day):
> ,----[ robert-pj-day ]
> | some colleagues are considering implementing some user space drivers
> | that need to recognize and process interrupts. i'm aware of the
> | possibilities -- UIO, for example -- but other than the technical
> | possibility of doing that, can anyone provide feedback on the
> | viability or benchmarking of that?
> |
> | is there an example someone can point at that demonstrates the
> | goodness or not of such an approach? has anyone out there done this,
> | and lived to regret it in terms of performance? thanks.
> `----
> well, dpdk folks seem to be doing just that for quite a while, and seem
> to be doing not too shabby in that space.
interesting ... downside is that that doesn't seem to run on
powerpc (which is the target platform i'm interested in here):
http://dpdk.org/
but still, i like the fact that it seems to support the idea that you
can run UIO and get adequate performance.
if anyone has any other examples like this, please pass them along.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2015-11-20 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 7:38 viability of supporting interrupts in user space driver? Robert P. J. Day
2015-11-20 8:40 ` Anupam Kapoor
2015-11-20 9:39 ` Robert P. J. Day [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=alpine.LFD.2.20.1511200437130.442@localhost \
--to=rpjday@crashcourse.ca \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).