From: anupam.kapoor@gmail.com (Anupam Kapoor)
To: kernelnewbies@lists.kernelnewbies.org
Subject: viability of supporting interrupts in user space driver?
Date: Fri, 20 Nov 2015 14:10:59 +0530 [thread overview]
Message-ID: <871tblhxlw.fsf@fatcat.parallelwireless> (raw)
In-Reply-To: <alpine.LFD.2.20.1511200236040.21896@localhost>
>>>>> [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.
--
kind regards
anupam
next prev parent reply other threads:[~2015-11-20 8:40 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 [this message]
2015-11-20 9:39 ` Robert P. J. Day
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=871tblhxlw.fsf@fatcat.parallelwireless \
--to=anupam.kapoor@gmail.com \
--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).