From: Sebastian Heidl <heidl@zib.de>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: doing a callback from the kernel to userspace
Date: Tue, 13 Nov 2001 10:47:09 +0100 [thread overview]
Message-ID: <20011113104709.C5446@csr-pc1.zib.de> (raw)
In-Reply-To: <20011112180505.A5446@csr-pc1.zib.de> <Pine.LNX.3.95.1011112133630.7750A-100000@chaos.analogic.com>
In-Reply-To: <Pine.LNX.3.95.1011112133630.7750A-100000@chaos.analogic.com>; from root@chaos.analogic.com on Mon, Nov 12, 2001 at 01:39:46PM -0500
On Mon, Nov 12, 2001 at 01:39:46PM -0500, Richard B. Johnson wrote:
> Please check the 'standard' ways of making drivers before you hack
> together something as Linux-specific as a kernel thread. I have
I think a kernel thread is not a choice for me as I truly want to execute
userspace code. As I said before: like a signal handler.
> drivers that are interrupted 10,000 times per second, transfer
> data from hardware buffers in 20,240 byte chunks at an overall
> transfer rate of 24 megabytes per second. The task(s) waiting
> for these data sleep in poll(), then call read() when data
> starts to arrive. This is the De-facto standard way for Unix
> systems. I don't have "latency" problems.
Well I'm talking about really fast networking so every _micro_second I save is
worth it. My numbers are a bit different: Think about a Gigabit-Ethernet card
sending you about 80000 interrupts if it's in a bad mood ;-)
To give you a figure: I'm trying to get below 10 us for user to user latency.
Have a look at the benchmarks at www.myri.com.
thanks anyway ;-)
_sh_
next prev parent reply other threads:[~2001-11-13 9:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 17:05 Sebastian Heidl
2001-11-12 18:39 ` Richard B. Johnson
2001-11-13 9:47 ` Sebastian Heidl [this message]
2001-11-12 18:27 Manfred Spraul
2001-11-13 9:47 ` Sebastian Heidl
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=20011113104709.C5446@csr-pc1.zib.de \
--to=heidl@zib.de \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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®