mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Erik Rigtorp <erik@rigtorp.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Monitoring file descriptors without switching context
Date: Mon, 11 Jan 2010 10:59:37 +0000	[thread overview]
Message-ID: <20100111105937.27d2a830@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <a57051ba1001110229q2ca28ffbqea37d07735debb52@mail.gmail.com>

> 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.

Alan

  reply	other threads:[~2010-01-11 10:55 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 [this message]
2010-01-11 11:51   ` Erik Rigtorp

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=20100111105937.27d2a830@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=erik@rigtorp.com \
    --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®