-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zach Brown wrote:
> 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:
All correct. I just want to point out that the proposed interface is
> 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Dumazet wrote:
> I am wondering if some parts are missing from your ChangeLog
>
> You apparently added in v3 a new 'flags' parameter to indirect syscall
> but no trace of this change in Changelog, and why it was added. This
> seems to imply a
Ulrich Drepper a écrit :
wing patches provide an alternative implementation of the
sys_indirect system call which has been discussed a few times.
This no system call allows us to extend existing system call
interfaces with adding more system calls.
I am wondering if some parts are missing from
Ulrich Drepper a écrit :
wing patches provide an alternative implementation of the
sys_indirect system call which has been discussed a few times.
This no system call allows us to extend existing system call
interfaces with adding more system calls.
I am wondering if some parts are missing from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Dumazet wrote:
I am wondering if some parts are missing from your ChangeLog
You apparently added in v3 a new 'flags' parameter to indirect syscall
but no trace of this change in Changelog, and why it was added. This
seems to imply a future
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zach Brown wrote:
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:
All correct. I just want to point out that the proposed interface is
sufficiently
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
wing patches provide an alternative implementation of the
sys_indirect system call which has been discussed a few times.
This no system call allows us to extend existing system call
interfaces with adding more system calls.
Davide's previous implementation is IMO far more complex than
warranted.
wing patches provide an alternative implementation of the
sys_indirect system call which has been discussed a few times.
This no system call allows us to extend existing system call
interfaces with adding more system calls.
Davide's previous implementation is IMO far more complex than
warranted.
10 matches
Mail list logo