linux-kernel - splitting work between user space program and the kernel

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

Date:	Thu, 30 Nov 2006 13:11:06 +0200
From:	"Yitzchak Eidus" <ieidus@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: splitting work between user space program and the kernel

i am looking to write a cluster program to linux.
each linux node will have to be connected in the network to other node.
in each node the kernel will have to know the "network information"
since i dont want to do the network work in the kernel and i want it
to be done in user space, i ask what is the best way to split the work
between the kernel and user space application that will interact with
each other...?
thanks
Yitzchak Eidus
-
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/