From: Erik Rigtorp <erik@rigtorp.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Monitoring file descriptors without switching context
Date: Mon, 11 Jan 2010 12:51:14 +0100 [thread overview]
Message-ID: <a57051ba1001110351sd288fk518d6dd9a58c8724@mail.gmail.com> (raw)
In-Reply-To: <20100111105937.27d2a830@lxorguk.ukuu.org.uk>
On Mon, Jan 11, 2010 at 11:59, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>> What I really need is some way to have the hardware block and monitor
>> IO for me. Would it be feasible to implement a special low latency
>> poll() syscall that uses MONITOR/MWAIT instructions to monitor file
>> descriptors?
>
> The futex locks are probably the lowest level interface you've got for
> interlocking between tasks and are very fast. You can also pin tasks to
> groups of cpus so you can create an I/O only core for example.
>
For core to core signaling the fastest way is to use a memory polling
loop. Cache control instructions allows me to make sure I use L3 for
intra-cpu communication. The problem is that I also need to monitor
file descriptors and if I can make them fast enough that would be
preferable because I'm also signaled when they close.
Erik
prev parent reply other threads:[~2010-01-11 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 10:29 Erik Rigtorp
2010-01-11 10:59 ` Alan Cox
2010-01-11 11:51 ` Erik Rigtorp [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=a57051ba1001110351sd288fk518d6dd9a58c8724@mail.gmail.com \
--to=erik@rigtorp.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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®