linux-kernel - Re: Monitoring file descriptors without switching context

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 11 Jan 2010 10:59:37 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Erik Rigtorp <erik@...torp.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Monitoring file descriptors without switching context

> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/