Messages in this thread | | | Date | Tue, 20 Nov 2007 10:08:31 -0800 | From | Zach Brown <> | Subject | Re: [PATCHv4 0/6] sys_indirect system call |
| |
> This was mentioned in one of my mails. I added the parameter to > accommodate Linus's and Zack's idea to use the functionality for syslets > as well. Not really a multiplexer, it is meant to be a "execute > synchronously or asynchronously" flag. In the latter case an additional > parameter might be needed to indicate the notification mechanism.
I'm sure the additional parameter will be needed, and it might be pretty involved. I think the current notion of syslets needs, at the very least:
- a userspace stack and IP to return to after going async - the completion context when completed async - a pointer to a return code when completed without blocking
We'll see. I'm working on it.
- z - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |