On Tue, 30 Oct 2007 16:55:25 +0100 Jan Kara <[EMAIL PROTECTED]> wrote:
> Hmm, that's right, but still the kernel->userspace interface could be via > netlink (which is much more flexible than signals etc.) and then in userspace > we could implement also some simple interface (UNIX socket?) for server like > apps... I think we all agree that it should not be a Unix signal, if only because glibc cannot manipulate memory pools from signal handlers :) The low memory message (for lack of a better word) needs to get to userspace over a file descriptor, which the process can select() or poll() on from its main loop. Whether that is a device node, a sysfs file, a netlink socket or something else ... I don't particularly care :) -- All Rights Reversed - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
