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] [day] [month] [year] [list]

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

On Mon, Jan 11, 2010 at 11:59, Alan Cox <alan@...rguk.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
--
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/